← previous blocknext block →recent activity
Analyzing
Block #89,757,866
42 transactions · 40 stateful · 2026-07-23 23:06:23 UTC
Parallelism
64/100
Blocked
75%
Avg conflicts / tx
4.76
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,757,866 · 42 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w210w011w112w013w014w115w116w217w218w319w420w321w522w623w424w725w826w527w928w1029w630w1131w1232w733w1335w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
30 touches
105 conflicts
0x92339d95…0800
0xb1c8ea…8888
28 touches
91 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xeed140a0…5a9c
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73f
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
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
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity