← previous blocknext block →recent activity
Analyzing
Block #91,797,808
25 transactions · 23 stateful · 2026-07-31 02:33:45 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,797,808 · 25 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
1w04w05w16w27w18w39w410w411w013w116w218w319w420w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xf12bbdae…d232
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x46cb45de…a566
0x188d58…ea8e
6 touches
3 conflicts
0x46cb45de…a568
0x188d58…ea8e
6 touches
3 conflicts
0x686bed17…7a81
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity