← previous blocknext block →recent activity
Analyzing
Block #86,315,297
15 transactions · 13 stateful · 2026-07-08 02:09:34 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,315,297 · 15 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
2w03w14w25w06w19w012w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0xbc169bf0…001e
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x9361e3b2…3bff
0x34b655…2a6f
4 touches
1 conflict
0x99e82227…2bda
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
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 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity