← previous blocknext block →recent activity
Analyzing
Block #86,506,991
16 transactions · 11 stateful · 2026-07-08 23:30:22 UTC
Parallelism
81/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,506,991 · 16 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x06ae4abf…656a
0x34b655…2a6f
2 touches
0 conflicts
0x0d5ba1f1…612e
0x34b655…2a6f
2 touches
0 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
2 touches
0 conflicts
0x3483ab79…8ed3
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 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity