← previous blocknext block →recent activity
Analyzing
Block #85,171,345
19 transactions · 19 stateful · 2026-07-02 19:03:34 UTC
Parallelism
58/100
Blocked
37%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,171,345 · 19 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
4w05w16w27w38w49w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb251976b…4938
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
12 touches
15 conflicts
0x51a914cf…a822
0x34b655…2a6f
12 touches
15 conflicts
0xd2a592d9…1a96
0x34b655…2a6f
12 touches
15 conflicts
0xe3ce9025…da31
0x34b655…2a6f
12 touches
15 conflicts
0xe732567d…b65d
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
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
28 conflicts on slot 0xb251976b09…9a4938
Audit this contract →
← previous block·next block →recent activity