← previous blocknext block →recent activity
Analyzing
Block #85,105,822
14 transactions · 14 stateful · 2026-07-02 11:46:28 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,105,822 · 14 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
1w02w03w14w28w19w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14f1bb26…8b4c
0x34b655…2a6f
8 touches
6 conflicts
0xc83310b1…c778
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3d381afb…8207
0x34b655…2a6f
8 touches
6 conflicts
0x06aed19e…ca57
0x34b655…2a6f
7 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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
6 conflicts on slot 0x14f1bb26e2…d68b4c
Audit this contract →
← previous block·next block →recent activity