← previous blocknext block →recent activity
Analyzing
Block #86,812,980
14 transactions · 14 stateful · 2026-07-10 09:37:25 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,812,980 · 14 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
1w02w13w26w07w08w19w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea83a1f2…18ce
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf7e59d30…11dd
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 0xea83a1f263…3818ce
Audit this contract →
← previous block·next block →recent activity