← previous blocknext block →recent activity
Analyzing
Block #86,300,051
20 transactions · 18 stateful · 2026-07-08 00:27:38 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,300,051 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w09w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x655939a8…0b3b
0x336ed4…c59c
14 touches
21 conflicts
0x00000000…000b
0x90c374…be45
14 touches
21 conflicts
0x00000000…000a
0x90c374…be45
14 touches
21 conflicts
0xe33999aa…8e37
0x8d1565…6723
14 touches
21 conflicts
0x2cbd9093…8a84
0x8d1565…6723
14 touches
21 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
14 touches
21 conflicts
0xfc111d09…525a
0x336ed4…c59c
14 touches
21 conflicts
0xaae376c7…d993
0x336ed4…c59c
13 touches
21 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
21 conflicts on slot 0x655939a8ca…fd0b3b
Audit this contract →
← previous block·next block →recent activity