← previous blocknext block →recent activity
Analyzing
Block #92,868,967
11 transactions · 11 stateful · 2026-08-03 20:22:49 UTC
Parallelism
36/100
Blocked
73%
Avg conflicts / tx
2.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,868,967 · 11 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
1w02w13w24w35w46w47w58w69w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd30f9e74…d404
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
10 touches
10 conflicts
0x4eab080a…d0e6
0x34b655…2a6f
8 touches
6 conflicts
0x825270f9…4547
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x240aec46…0b68
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
21 conflicts on slot 0xd30f9e74d6…9ed404
Audit this contract →
← previous block·next block →recent activity