← previous blocknext block →recent activity
Analyzing
Block #85,210,617
10 transactions · 10 stateful · 2026-07-02 23:25:06 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,210,617 · 10 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0xd1fe26e6…8d31
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x03d4f4ad…f6df
0x065c9d…c394
2 touches
0 conflicts
0x34ad6d15…c915
0x065c9d…c394
2 touches
0 conflicts
0x58f93627…023e
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
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
1 conflict on slot 0x0aa5b76bf8…b060db
Audit this contract →
← previous block·next block →recent activity