← previous blocknext block →recent activity
Analyzing
Block #86,674,312
26 transactions · 25 stateful · 2026-07-09 18:11:21 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,674,312 · 26 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
1w02w13w24w35w46w07w111w012w015w016w217w118w120w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a870d86…79ef
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0x2eb48eb7…9d68
0x8d1565…6723
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc88f593e…5d93
0x336ed4…c59c
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: 0x336ed437…cfc59c
10 conflicts on slot 0x4a870d863e…7379ef
Audit this contract →
← previous block·next block →recent activity