← previous blocknext block →recent activity
Analyzing
Block #90,818,583
40 transactions · 36 stateful · 2026-07-27 16:24:22 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
1.8
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #90,818,583 · 40 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w511w616w917w1022w323w124w1126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0xb476ee35…c627
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x0110331c…b891
0x34b655…2a6f
6 touches
3 conflicts
0x8be9b6bc…3a1d
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity