← previous blocknext block →recent activity
Analyzing
Block #90,440,047
35 transactions · 33 stateful · 2026-07-26 08:39:38 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.54
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #90,440,047 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w210w015w116w220w321w422w523w624w725w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c919423…d2c8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x0168ce43…cd66
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x78255c70…2733
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x4c9194238b…19d2c8
Audit this contract →
← previous block·next block →recent activity