← previous blocknext block →recent activity
Analyzing
Block #86,784,428
16 transactions · 15 stateful · 2026-07-10 06:26:41 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,784,428 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w210w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddf1cf9…a8ba
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8de38574…ad6e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x44231245…5442
0x34b655…2a6f
4 touches
1 conflict
0x666b28db…11f0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: Perpl
3 conflicts on slot 0x5ddf1cf984…d5a8ba
Audit this contract →
← previous block·next block →recent activity