← previous blocknext block →recent activity
Analyzing
Block #85,159,544
20 transactions · 19 stateful · 2026-07-02 17:45:07 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,159,544 · 20 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
3w05w06w17w28w39w410w511w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xb44d5376…33cc
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x4dbbe989…6aa7
0x34b655…2a6f
12 touches
15 conflicts
0x548145a9…cfce
0x34b655…2a6f
12 touches
15 conflicts
0x63b15849…80b2
0x34b655…2a6f
12 touches
15 conflicts
0x06aed19e…ca57
0x34b655…2a6f
12 touches
15 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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity