← previous blocknext block →recent activity
Analyzing
Block #92,313,212
11 transactions · 10 stateful · 2026-08-01 21:46:11 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,313,212 · 11 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
1w07w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x0df13365…7c52
0x34b655…2a6f
4 touches
1 conflict
0x21605a79…d719
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x454a7ad6…a4b2
0x34b655…2a6f
4 touches
1 conflict
0x50e1b865…3b79
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