← previous blocknext block →recent activity
Analyzing
Block #98,356,111
11 transactions · 11 stateful · 2026-08-23 02:10:38 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,356,111 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ce08c09…7f3e
0xa6afd3…d132
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0xdf352747…7eaf
0x34b655…2a6f
4 touches
1 conflict
0xee75c266…f8c6
0x34b655…2a6f
4 touches
1 conflict
0xf06fce24…887d
0x34b655…2a6f
4 touches
1 conflict
0xfe1f5ba4…ee77
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
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-WETH/USDC
1 conflict on slot 0x5ce08c0960…b77f3e
Audit this contract →
← previous block·next block →recent activity