← previous blocknext block →recent activity
Analyzing
Block #85,109,689
18 transactions · 17 stateful · 2026-07-02 12:12:15 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,109,689 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w19w010w211w112w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b3209b…f766
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x98834cc0…6c23
0x34b655…2a6f
6 touches
3 conflicts
0x25a11da1…46af
0x34b655…2a6f
6 touches
3 conflicts
0x6db97e95…8353
0x34b655…2a6f
4 touches
1 conflict
0x8bf45ac2…10ac
0x34b655…2a6f
4 touches
1 conflict
0x91354d2f…b97b
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x79b3209b12…57f766
Audit this contract →
← previous block·next block →recent activity