← previous blocknext block →recent activity
Analyzing
Block #86,774,287
26 transactions · 24 stateful · 2026-07-10 05:19:04 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,774,287 · 26 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
1w02w15w06w19w211w318w323w024w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
6 touches
3 conflicts
0x9adb2803…81f1
0x34b655…2a6f
4 touches
1 conflict
0xa444004d…1c9f
0x34b655…2a6f
4 touches
1 conflict
0xa444004d…1ca0
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity