← previous blocknext block →recent activity
Analyzing
Block #89,872,660
42 transactions · 40 stateful · 2026-07-24 08:45:21 UTC
Parallelism
57/100
Blocked
70%
Avg conflicts / tx
4.33
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #89,872,660 · 42 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w315w116w217w318w020w122w225w327w429w530w631w732w833w934w1035w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
36 touches
153 conflicts
0x92339d95…0800
0xb1c8ea…8888
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x32409e80…a396
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xbe0321db…dcb1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
153 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity