← previous blocknext block →recent activity
Analyzing
Block #90,622,935
30 transactions · 24 stateful · 2026-07-27 00:00:00 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,622,935 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w29w310w411w512w013w114w217w218w120w321w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x17e90565…d957
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity