← previous blocknext block →recent activity
Analyzing
Block #86,611,558
28 transactions · 26 stateful · 2026-07-09 11:10:59 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,611,558 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w211w112w013w114w318w019w121w022w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x033ddbe8…850a
0x34b655…2a6f
4 touches
1 conflict
0x0ad016fd…1ebc
0x34b655…2a6f
4 touches
1 conflict
0x11238840…69c5
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x12573732…e891
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity