← previous blocknext block →recent activity
Analyzing
Block #98,645,905
24 transactions · 23 stateful · 2026-08-24 02:55:36 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,645,905 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w010w011w212w314w016w317w119w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x56f12a77…7c62
0x34b655…2a6f
4 touches
1 conflict
0x6a729fee…566a
0x34b655…2a6f
4 touches
1 conflict
0x6d6bf6fe…66e4
0x34b655…2a6f
4 touches
1 conflict
0x9492fc9c…ef15
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity