← previous blocknext block →recent activity
Analyzing
Block #92,806,246
20 transactions · 20 stateful · 2026-08-03 15:07:08 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,806,246 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w07w19w111w213w115w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17091c69…e7f3
0x34b655…2a6f
4 touches
1 conflict
0x1ed748d8…d530
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x69ae0f00…1d30
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 0x17091c6991…8de7f3
Audit this contract →
← previous block·next block →recent activity