← previous blocknext block →recent activity
Analyzing
Block #86,225,267
22 transactions · 17 stateful · 2026-07-07 16:08:23 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,225,267 · 22 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
1w02w03w14w25w36w47w18w29w010w111w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc88f593e…5d93
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
8 touches
6 conflicts
0x79250c04…e936
0x8d1565…6723
6 touches
3 conflicts
0x4a870d86…79ef
0x336ed4…c59c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3e6302c8…64f5
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: 0x336ed437…cfc59c
10 conflicts on slot 0xc88f593e3b…e65d93
Audit this contract →
← previous block·next block →recent activity