← previous blocknext block →recent activity
Analyzing
Block #89,881,054
40 transactions · 34 stateful · 2026-07-24 09:27:34 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
3.55
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,881,054 · 40 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
4w07w111w012w013w114w115w216w217w318w420w521w623w725w827w928w329w1030w431w1133w1234w535w1336w637w1438w739w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
30 touches
105 conflicts
0x92339d95…0800
0x0000a8…8888
18 touches
36 conflicts
0xd68cd74f…9826
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x48315f67…c1a6
0x34b655…2a6f
2 touches
0 conflicts
0x699ee60f…de01
0x34b655…2a6f
2 touches
0 conflicts
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: 0xb1c8ead4…c38888
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity