← previous blocknext block →recent activity
Analyzing
Block #85,853,212
19 transactions · 18 stateful · 2026-07-05 22:45:51 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,853,212 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w06w17w28w39w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x44ad89ba…cf83
0x0a917f…7777
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0x1ccfa324…0b93
0x0a917f…7777
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xe6f2ae57…2026
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
8 touches
6 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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity