← previous blocknext block →recent activity
Analyzing
Block #86,629,016
30 transactions · 20 stateful · 2026-07-09 13:07:30 UTC
Parallelism
90/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,629,016 · 30 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w17w08w19w010w011w013w114w116w225w026w127w028w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a4c3d20…bd65
0x3bd359…433a
6 touches
3 conflicts
0x0db0aaac…e94d
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0000
0x4a92f8…f3d6
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
6 touches
3 conflicts
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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: Wrapped MON (WMON)
3 conflicts on slot 0x4a4c3d20ec…42bd65
Audit this contract →
← previous block·next block →recent activity