← previous blocknext block →recent activity
Analyzing
Block #89,750,196
20 transactions · 16 stateful · 2026-07-23 22:27:42 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,750,196 · 20 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
2w03w04w15w26w37w08w111w014w115w217w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe8d8a9a2…40f3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
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: Settlement / Helper
6 conflicts on slot 0x5778d110c4…8ad2e6
Audit this contract →
← previous block·next block →recent activity