← previous blocknext block →recent activity
Analyzing
Block #92,114,524
10 transactions · 10 stateful · 2026-08-01 05:06:54 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,114,524 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd46bf0c0…b1be
0x34b655…2a6f
4 touches
1 conflict
0xe7ceda84…1a3e
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
1 conflict on slot 0xf63c2a2b51…78bc60
Audit this contract →
← previous block·next block →recent activity