← previous blocknext block →recent activity
Analyzing
Block #86,192,551
17 transactions · 16 stateful · 2026-07-07 12:29:53 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,192,551 · 17 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
1w02w13w24w35w46w07w18w210w311w012w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93c58e4d…9b32
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x47d4745e…02bb
0x336ed4…c59c
10 touches
10 conflicts
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0x085c9fac…8fcf
0x8d1565…6723
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0x034f1f86…4e8d
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: 0x336ed437…cfc59c
10 conflicts on slot 0x93c58e4dd7…459b32
Audit this contract →
← previous block·next block →recent activity