← previous blocknext block →recent activity
Analyzing
Block #85,140,829
39 transactions · 30 stateful · 2026-07-02 15:40:27 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,140,829 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w19w211w012w113w315w117w528w629w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe49cc2eb…85fd
0xd32edf…ff58
9 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0002
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
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 0xcdc1731c6b…b6b91a
Audit this contract →
← previous block·next block →recent activity