← previous blocknext block →recent activity
Analyzing
Block #89,770,564
40 transactions · 36 stateful · 2026-07-24 00:10:32 UTC
Parallelism
68/100
Blocked
75%
Avg conflicts / tx
3.7
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,770,564 · 40 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
1w02w13w05w17w09w111w214w015w016w117w118w219w220w321w322w423w424w525w626w527w728w829w630w932w734w835w936w1037w1139w12
- 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
24 touches
66 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x74a2c581…c965
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
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