← previous blocknext block →recent activity
Analyzing
Block #91,009,838
30 transactions · 27 stateful · 2026-07-28 08:27:14 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.27
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,009,838 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w08w19w210w311w413w516w318w619w425w126w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc6b1d981…1be2
0xa6afd3…d132
10 touches
10 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity