← previous blocknext block →recent activity
Analyzing
Block #86,962,119
15 transactions · 14 stateful · 2026-07-11 02:14:31 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,962,119 · 15 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
2w03w14w25w39w410w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa112f315…1a92
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9ad0eb5b…7a1b
0x34b655…2a6f
6 touches
3 conflicts
0x1fc9dceb…9e8b
0x34b655…2a6f
4 touches
1 conflict
0x43cea534…ddce
0x34b655…2a6f
4 touches
1 conflict
0x453f53a8…e541
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity