← previous blocknext block →recent activity
Analyzing
Block #89,749,801
49 transactions · 46 stateful · 2026-07-23 22:25:43 UTC
Parallelism
61/100
Blocked
80%
Avg conflicts / tx
4.92
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #89,749,801 · 49 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w111w113w214w315w416w517w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
38 touches
171 conflicts
0x92339d95…0800
0xb1c8ea…8888
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x5484fc7f…a8d8
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
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: 0x0000a8fd…758888
171 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity