← previous blocknext block →recent activity
Analyzing
Block #84,099,963
19 transactions · 18 stateful · 2026-06-27 20:00:11 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,099,963 · 19 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
1w06w09w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5df6102c…6494
0xa6afd3…d132
6 touches
3 conflicts
0x7b7af531…48f1
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x07726b38…b244
0xa6afd3…d132
3 touches
1 conflict
0xba6a7f36…20bd
0xa6afd3…d132
3 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
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-WETH/USDC
3 conflicts on slot 0x5df6102cfc…c86494
Audit this contract →
← previous block·next block →recent activity