← previous blocknext block →recent activity
Analyzing
Block #85,972,218
22 transactions · 18 stateful · 2026-07-06 11:58:51 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,972,218 · 22 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
3w014w115w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0x6fc24f20…f3c7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0001
0x630933…e4df
2 touches
0 conflicts
0x00000000…0002
0x630933…e4df
2 touches
0 conflicts
0x30904ae7…7250
0x754704…b603
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