← previous blocknext block →recent activity
Analyzing
Block #85,994,072
21 transactions · 18 stateful · 2026-07-06 14:24:59 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,994,072 · 21 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
1w06w011w112w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x62a9d74b…2d37
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity