← previous blocknext block →recent activity
Analyzing
Block #86,456,131
12 transactions · 10 stateful · 2026-07-08 17:50:25 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,456,131 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x485ae99d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x250c8181…eef2
0x34b655…2a6f
3 touches
1 conflict
0x0f13d630…5be3
0x34b655…2a6f
2 touches
0 conflicts
0x3c343a12…f65e
0x34b655…2a6f
2 touches
0 conflicts
0x4e460439…5ba2
0x34b655…2a6f
2 touches
0 conflicts
0x5b4542d8…05f4
0x34b655…2a6f
2 touches
0 conflicts
0x5b813b1d…5968
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity