← previous blocknext block →recent activity
Analyzing
Block #86,082,236
18 transactions · 14 stateful · 2026-07-07 00:13:28 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,082,236 · 18 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
3w05w06w110w211w115w016w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf7ce7a7…1d9e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x663d3288…f460
0x34b655…2a6f
4 touches
1 conflict
0x9361e3b2…3bff
0x34b655…2a6f
4 touches
1 conflict
0x9999697f…3d79
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 0xbf7ce7a7c2…cf1d9e
Audit this contract →
← previous block·next block →recent activity