← previous blocknext block →recent activity
Analyzing
Block #92,525,354
19 transactions · 19 stateful · 2026-08-02 15:33:05 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,525,354 · 19 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
2w03w14w05w16w27w08w19w010w111w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xb6cf98c1…cf0c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x342222e8…2ec4
0x34b655…2a6f
4 touches
1 conflict
0x594cdd05…231a
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
3 conflicts on slot 0xb15c58ec9b…35bd83
Audit this contract →
← previous block·next block →recent activity