← previous blocknext block →recent activity
Analyzing
Block #86,328,960
15 transactions · 13 stateful · 2026-07-08 03:40:48 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,328,960 · 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
1w03w06w18w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503b3a72…f6df
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x40f5e9c0…60d5
0x34b655…2a6f
4 touches
1 conflict
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
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
3 conflicts on slot 0x503b3a72dc…c4f6df
Audit this contract →
← previous block·next block →recent activity