← previous blocknext block →recent activity
Analyzing
Block #92,536,640
8 transactions · 8 stateful · 2026-08-02 16:29:50 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,536,640 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47da1e40…7158
0x34b655…2a6f
8 touches
6 conflicts
0xfd91146e…d227
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xef103835…92e7
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
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 0x47da1e4031…2a7158
Audit this contract →
← previous block·next block →recent activity