← previous blocknext block →recent activity
Analyzing
Block #85,123,505
45 transactions · 41 stateful · 2026-07-02 13:44:44 UTC
Parallelism
56/100
Blocked
73%
Avg conflicts / tx
3.64
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,123,505 · 45 txs across 20 waves · depth 20
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
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w39w410w512w013w114w216w017w118w219w334w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
24 touches
66 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
20 touches
45 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
20 touches
45 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
20 touches
45 conflicts
0x43ffd8bd…0d0c
0x34b655…2a6f
18 touches
39 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity