← previous blocknext block →recent activity
Analyzing
Block #92,163,539
14 transactions · 14 stateful · 2026-08-01 09:13:27 UTC
Parallelism
43/100
Blocked
57%
Avg conflicts / tx
1.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,163,539 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w69w710w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21a4941a…e7d2
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x29c1a140…099f
0x34b655…2a6f
8 touches
6 conflicts
0xa57d17f0…672a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x28f324ed…9db7
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 0x21a4941aa8…b6e7d2
Audit this contract →
← previous block·next block →recent activity