← previous blocknext block →recent activity
Analyzing
Block #91,408,473
45 transactions · 36 stateful · 2026-07-29 17:54:09 UTC
Parallelism
78/100
Blocked
81%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,408,473 · 45 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w311w412w413w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xa1ff0729…0146
0xa6afd3…d132
12 touches
15 conflicts
0x890a1db9…1712
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 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: 0x48cba278…e2b48b
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity