← previous blocknext block →recent activity
Analyzing
Block #85,168,612
19 transactions · 17 stateful · 2026-07-02 18:45:25 UTC
Parallelism
47/100
Blocked
65%
Avg conflicts / tx
2.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,168,612 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w411w312w413w515w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x7ae63663…9d94
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x97c67486…27fe
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity