← previous blocknext block →recent activity
Analyzing
Block #86,978,956
12 transactions · 11 stateful · 2026-07-11 04:06:58 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,978,956 · 12 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
2w03w14w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b75f0c2…d323
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xbf47a88f…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xc50ac7d4…e964
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: Perpl
3 conflicts on slot 0x6b75f0c27b…f5d323
Audit this contract →
← previous block·next block →recent activity