← previous blocknext block →recent activity
Analyzing
Block #86,328,415
10 transactions · 9 stateful · 2026-07-08 03:37:10 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,328,415 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x75cc4b3f…d680
0x34b655…2a6f
4 touches
1 conflict
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0x1e7e4246…4872
0x34b655…2a6f
2 touches
0 conflicts
0x1fdab584…f092
0x34b655…2a6f
2 touches
0 conflicts
0x27a38232…84ce
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 0xec0e022022…becb90
Audit this contract →
← previous block·next block →recent activity