← previous blocknext block →recent activity
Analyzing
Block #85,131,495
38 transactions · 32 stateful · 2026-07-02 14:38:10 UTC
Parallelism
66/100
Blocked
63%
Avg conflicts / tx
2.16
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #85,131,495 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w314w015w116w217w318w419w520w621w727w428w130w136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
12 touches
15 conflicts
0x85631114…3ff6
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity