← previous blocknext block →recent activity
Analyzing
Block #92,601,568
24 transactions · 23 stateful · 2026-08-02 21:56:24 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,601,568 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w210w011w112w013w314w415w517w619w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xef1de905…0582
0x34b655…2a6f
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0x845baaac…a8ea
0x34b655…2a6f
5 touches
3 conflicts
0xb7fb66e8…4f94
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
21 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity