← previous blocknext block →recent activity
Analyzing
Block #89,560,225
63 transactions · 50 stateful · 2026-07-23 03:50:26 UTC
Parallelism
75/100
Blocked
74%
Avg conflicts / tx
2.3
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #89,560,225 · 63 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w18w113w015w016w017w118w219w321w423w524w425w627w150w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x8bc2cc4c…4434
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd6c0349d…05b0
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 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
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity