← previous blocknext block →recent activity
Analyzing
Block #86,250,323
20 transactions · 19 stateful · 2026-07-07 18:55:49 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,250,323 · 20 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
1w02w14w05w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf94f773…2dae
0x34b655…2a6f
4 touches
1 conflict
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x097b4de6…ed0c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0x8945aaf7…b779
0xd32edf…ff58
3 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 0xcf94f7732a…5c2dae
Audit this contract →
← previous block·next block →recent activity