← previous blocknext block →recent activity
Analyzing
Block #86,531,831
21 transactions · 20 stateful · 2026-07-09 02:16:11 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,531,831 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w612w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x73e9b8f6…ed9d
0x34b655…2a6f
10 touches
10 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
10 touches
10 conflicts
0x06aed19e…ca57
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0xb0bc3bf8…e2b1
0x34b655…2a6f
10 touches
10 conflicts
0xcaa1fc83…36e9
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity