← previous blocknext block →recent activity
Analyzing
Block #86,626,359
13 transactions · 11 stateful · 2026-07-09 12:49:46 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,626,359 · 13 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
4w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x184cafae…fb7d
0x34b655…2a6f
2 touches
0 conflicts
0x18c1a977…9924
0x34b655…2a6f
2 touches
0 conflicts
0x32cd26f2…e1ff
0x34b655…2a6f
2 touches
0 conflicts
0x5efa0d16…4a5d
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 0x326f2a0070…43a2a6
Audit this contract →
← previous block·next block →recent activity