← previous blocknext block →recent activity
Analyzing
Block #90,623,353
16 transactions · 16 stateful · 2026-07-27 00:02:06 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,623,353 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w39w410w111w512w213w315w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7032dc14…49ea
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
6 touches
3 conflicts
0x17e90565…d957
0xa6afd3…d132
6 touches
3 conflicts
0x70cfbacf…5c46
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x73c862b9…a0af
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 0x7032dc1485…0e49ea
Audit this contract →
← previous block·next block →recent activity