← previous blocknext block →recent activity
Analyzing
Block #86,933,252
12 transactions · 9 stateful · 2026-07-10 23:01:38 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,933,252 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba014e3…35d5
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x34b6e036…2161
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e18a909…378a
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
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 0x3ba014e38a…cf35d5
Audit this contract →
← previous block·next block →recent activity