← previous blocknext block →recent activity
Analyzing
Block #91,957,535
24 transactions · 24 stateful · 2026-07-31 15:57:21 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,957,535 · 24 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
1w02w13w05w16w07w18w19w210w311w214w015w117w019w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf845b6ce…0547
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x03b16972…8f62
0x34b655…2a6f
6 touches
3 conflicts
0x6459805c…615d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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 0xf845b6cedf…910547
Audit this contract →
← previous block·next block →recent activity