← previous blocknext block →recent activity
Analyzing
Block #92,807,058
24 transactions · 22 stateful · 2026-08-03 15:11:13 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,807,058 · 24 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
1w02w03w15w16w27w38w39w412w519w020w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
12 touches
15 conflicts
0x3f70f62c…50da
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x05349083…7807
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x2bbc0cfb…c2be
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity