← previous blocknext block →recent activity
Analyzing
Block #85,173,736
19 transactions · 19 stateful · 2026-07-02 19:19:31 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,173,736 · 19 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
1w02w13w24w35w46w515w016w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a7428b…ddf3
0x34b655…2a6f
12 touches
15 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0xa457c06e…2f06
0x34b655…2a6f
10 touches
10 conflicts
0x16b3a441…13db
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x51a914cf…a822
0x34b655…2a6f
10 touches
10 conflicts
0x9c2e5d14…f8ae
0x34b655…2a6f
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
15 conflicts on slot 0x05a7428b79…6cddf3
Audit this contract →
← previous block·next block →recent activity