← previous blocknext block →recent activity
Analyzing
Block #92,372,224
19 transactions · 15 stateful · 2026-08-02 02:42:57 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,372,224 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w410w511w612w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
12 touches
15 conflicts
0xb293de31…593a
0x34b655…2a6f
10 touches
10 conflicts
0x7bf6a41f…a17d
0x34b655…2a6f
8 touches
6 conflicts
0x928f6d82…20bb
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a8
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity