← previous blocknext block →recent activity
Analyzing
Block #92,311,020
13 transactions · 13 stateful · 2026-08-01 21:35:10 UTC
Parallelism
46/100
Blocked
62%
Avg conflicts / tx
2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,311,020 · 13 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
1w03w14w25w37w48w59w310w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa399fba3…eeb4
0x34b655…2a6f
12 touches
15 conflicts
0x94aff148…b584
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xe3dfc92b…3687
0x34b655…2a6f
6 touches
3 conflicts
0x5b87d3ff…d2fe
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 0xa399fba3c9…0aeeb4
Audit this contract →
← previous block·next block →recent activity