← previous blocknext block →recent activity
Analyzing
Block #92,561,532
64 transactions · 61 stateful · 2026-08-02 18:35:01 UTC
Parallelism
91/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,561,532 · 64 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w38w49w561w062w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e2685de…dbbe
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x6e2685def9…8edbbe
Audit this contract →
← previous block·next block →recent activity