← previous blocknext block →recent activity
Analyzing
Block #86,856,309
22 transactions · 20 stateful · 2026-07-10 14:27:12 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,856,309 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w411w012w114w516w620w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3133f94b…f76b
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x288bc578…318e
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
6 touches
3 conflicts
0x69613cc6…2d0d
0x34b655…2a6f
6 touches
3 conflicts
0x6d94347e…768b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity