← previous blocknext block →recent activity
Analyzing
Block #86,683,824
10 transactions · 8 stateful · 2026-07-09 19:14:52 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,683,824 · 10 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
5w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0fb72b9…2d6d
0x34b655…2a6f
4 touches
1 conflict
0x17c40594…7e17
0x34b655…2a6f
4 touches
1 conflict
0x304b87aa…e898
0x34b655…2a6f
4 touches
1 conflict
0x3dc8c985…3625
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x501cdafe…9628
0x34b655…2a6f
4 touches
1 conflict
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
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
1 conflict on slot 0xd0fb72b914…4e2d6d
Audit this contract →
← previous block·next block →recent activity