← previous blocknext block →recent activity
Analyzing
Block #89,771,581
46 transactions · 41 stateful · 2026-07-24 00:15:39 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
3.57
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,771,581 · 46 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w112w113w215w116w017w018w119w221w322w424w525w626w127w728w829w230w931w1032w333w1134w435w536w637w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
28 touches
91 conflicts
0x92339d95…0800
0xb1c8ea…8888
24 touches
66 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x4c7c8c7f…d6fa
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
91 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity