← previous blocknext block →recent activity
Analyzing
Block #92,244,853
19 transactions · 18 stateful · 2026-08-01 16:02:21 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,244,853 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w59w010w111w214w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa3f21179…15db
0x34b655…2a6f
8 touches
6 conflicts
0xfb887a94…c508
0x34b655…2a6f
6 touches
3 conflicts
0x38c3bb6d…3bae
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity