← previous blocknext block →recent activity
Analyzing
Block #86,256,943
20 transactions · 16 stateful · 2026-07-07 19:40:03 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,256,943 · 20 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
1w05w06w18w09w110w111w114w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x2a9092cb…64ee
0x34b655…2a6f
4 touches
1 conflict
0x62eef491…6f31
0x34b655…2a6f
4 touches
1 conflict
0x928d962f…f990
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xb503dcab…7c61
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