← previous blocknext block →recent activity
Analyzing
Block #85,130,186
21 transactions · 20 stateful · 2026-07-02 14:29:24 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,130,186 · 21 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
1w02w03w15w06w17w28w19w112w216w217w318w419w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08d66073…e706
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe96e3c16…a9f3
0x34b655…2a6f
8 touches
6 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0x305e6edb…89b1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe68e2a81…3be7
0x34b655…2a6f
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 0x08d6607389…0fe706
Audit this contract →
← previous block·next block →recent activity