← previous blocknext block →recent activity
Analyzing
Block #85,184,163
62 transactions · 53 stateful · 2026-07-02 20:29:01 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
2.74
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,184,163 · 62 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w19w211w113w016w117w418w522w235w642w643w744w245w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xa678cd56…4fab
0x34b655…2a6f
12 touches
15 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
12 touches
15 conflicts
0xdcf90674…5bf6
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x08a70830…66e3
0xd32edf…ff58
9 touches
10 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity