← previous blocknext block →recent activity
Analyzing
Block #86,687,456
14 transactions · 11 stateful · 2026-07-09 19:39:06 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,687,456 · 14 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
4w06w07w18w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91ef27f5…9eab
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac2a3901…aca4
0x34b655…2a6f
4 touches
1 conflict
0xdb94d57f…4889
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3426
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3427
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0x91ef27f5fb…de9eab
Audit this contract →
← previous block·next block →recent activity