← previous blocknext block →recent activity
Analyzing
Block #92,299,637
16 transactions · 15 stateful · 2026-08-01 20:37:54 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,299,637 · 16 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
1w02w13w24w25w36w47w510w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
12 touches
15 conflicts
0x5416be33…6b44
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc9c31a7c…a75e
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x99bd8bbd…b52c
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 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity