← previous blocknext block →recent activity
Analyzing
Block #85,157,825
19 transactions · 18 stateful · 2026-07-02 17:33:40 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,157,825 · 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
3w04w15w26w37w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3ef0af63…992e
0x34b655…2a6f
8 touches
6 conflicts
0x343db577…2962
0x34b655…2a6f
4 touches
1 conflict
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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity