← previous blocknext block →recent activity
Analyzing
Block #89,857,808
36 transactions · 33 stateful · 2026-07-24 07:30:38 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
3.19
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #89,857,808 · 36 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w19w214w015w016w117w118w219w220w321w322w423w424w525w526w627w628w729w730w831w932w833w1034w935w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
24 touches
66 conflicts
0x92339d95…0800
0xb1c8ea…8888
20 touches
45 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb8806526…e31f
0x34b655…2a6f
4 touches
1 conflict
0x92a2c049…0ed8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x44f26cbe…58c2
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
66 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity