← previous blocknext block →recent activity
Analyzing
Block #89,874,035
33 transactions · 32 stateful · 2026-07-24 08:52:15 UTC
Parallelism
51/100
Blocked
72%
Avg conflicts / tx
4.33
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #89,874,035 · 33 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w18w210w011w012w113w114w215w316w217w418w519w320w621w722w423w824w525w926w627w1028w1129w1230w1331w1432w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
32 touches
120 conflicts
0x92339d95…0800
0xb1c8ea…8888
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
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: 0x0000a8fd…758888
120 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity