← previous blocknext block →recent activity
Analyzing
Block #98,413,831
14 transactions · 13 stateful · 2026-08-23 07:01:02 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,413,831 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
4 touches
1 conflict
0x42e5184f…4e8c
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity