← previous blocknext block →recent activity
Analyzing
Block #92,006,846
24 transactions · 21 stateful · 2026-07-31 20:05:21 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,006,846 · 24 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
1w02w13w24w05w06w17w29w011w313w114w119w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xadb0aec6…48ee
0x34b655…2a6f
6 touches
3 conflicts
0x1eb410fd…591d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2c4b137d…a649
0xd32edf…ff58
5 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x56eee92a…6928
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity