← previous blocknext block →recent activity
Analyzing
Block #86,492,334
22 transactions · 20 stateful · 2026-07-08 21:52:38 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,492,334 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w08w19w210w313w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x452f2538…1cfc
0x34b655…2a6f
6 touches
3 conflicts
0x6827c800…a1a1
0x34b655…2a6f
6 touches
3 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x667627cc…be4b
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity