← previous blocknext block →recent activity
Analyzing
Block #92,525,698
12 transactions · 11 stateful · 2026-08-02 15:34:49 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,525,698 · 12 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
2w04w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5ba139…ea6f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec181933…425b
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1f02c5ca…02d7
0x34b655…2a6f
4 touches
1 conflict
0x22fbc359…e556
0x34b655…2a6f
4 touches
1 conflict
0x3fb7b13e…9cd9
0x34b655…2a6f
4 touches
1 conflict
0x605f05fa…4ebc
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 0xab5ba139f3…9fea6f
Audit this contract →
← previous block·next block →recent activity