← previous blocknext block →recent activity
Analyzing
Block #89,852,837
34 transactions · 32 stateful · 2026-07-24 07:05:38 UTC
Parallelism
50/100
Blocked
75%
Avg conflicts / tx
5.06
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,852,837 · 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
8w09w010w111w112w213w214w315w316w417w418w519w520w621w622w723w824w725w826w927w1028w1129w1230w1331w1432w1533w16
- 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
18 touches
36 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
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: 0x0000a8fd…758888
136 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity