← previous blocknext block →recent activity
Analyzing
Block #92,188,805
14 transactions · 13 stateful · 2026-08-01 11:20:30 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,188,805 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w512w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0xd7320039…3bbf
0x34b655…2a6f
6 touches
3 conflicts
0x631d80dd…916e
0x34b655…2a6f
4 touches
1 conflict
0x654a3ddd…a671
0x34b655…2a6f
4 touches
1 conflict
0x6989456e…7ae0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity