← previous blocknext block →recent activity
Analyzing
Block #86,701,439
31 transactions · 25 stateful · 2026-07-09 21:12:22 UTC
Parallelism
84/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,701,439 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w311w412w416w017w118w221w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x8044255c…fa4f
0xd32edf…ff58
9 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x34443913…cbf3
0x336ed4…c59c
8 touches
6 conflicts
0x4a870d86…79ef
0x336ed4…c59c
8 touches
6 conflicts
0x2eb48eb7…9d68
0x8d1565…6723
8 touches
6 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: 0x8d156514…236723
10 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity