← previous blocknext block →recent activity
Analyzing
Block #92,692,492
17 transactions · 16 stateful · 2026-08-03 05:34:37 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,692,492 · 17 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
1w02w13w24w37w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02991b41…19e6
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf76df566…dffd
0x34b655…2a6f
8 touches
6 conflicts
0x41515e30…4198
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
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
15 conflicts on slot 0x02991b41c5…1a19e6
Audit this contract →
← previous block·next block →recent activity