← previous blocknext block →recent activity
Analyzing
Block #89,864,776
34 transactions · 33 stateful · 2026-07-24 08:05:41 UTC
Parallelism
50/100
Blocked
76%
Avg conflicts / tx
4.79
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,864,776 · 34 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w310w011w012w113w114w215w216w317w318w421w522w624w725w826w927w1028w1129w1230w1331w1432w1533w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
34 touches
136 conflicts
0x92339d95…0800
0xb1c8ea…8888
14 touches
21 conflicts
0x2441f935…0d11
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xee8237bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x0bcbbcad…fc9c
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
136 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity