← previous blocknext block →recent activity
Analyzing
Block #89,770,220
42 transactions · 38 stateful · 2026-07-24 00:08:48 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
3.33
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,770,220 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w010w011w112w214w015w017w119w220w322w423w524w125w627w230w333w434w535w636w737w838w939w1040w1141w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
26 touches
78 conflicts
0x92339d95…0800
0xb1c8ea…8888
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x86c98782…f3b7
0x34b655…2a6f
4 touches
1 conflict
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
78 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity