← previous blocknext block →recent activity
Analyzing
Block #86,977,974
9 transactions · 8 stateful · 2026-07-11 04:00:24 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,977,974 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf66a16ae…0da8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00a91074…b3a8
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0e403c18…eac8
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xf66a16ae36…390da8
Audit this contract →
← previous block·next block →recent activity