← previous blocknext block →recent activity
Analyzing
Block #89,711,173
18 transactions · 15 stateful · 2026-07-23 19:10:33 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,711,173 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w010w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x9932c6d5…0e65
0x0a2fbf…29b1
4 touches
1 conflict
0x9932c6d5…0e66
0x0a2fbf…29b1
4 touches
1 conflict
0x9932c6d5…0e69
0x0a2fbf…29b1
4 touches
1 conflict
0xbfe60507…e208
0x0a2fbf…29b1
4 touches
1 conflict
0xbfe60507…e209
0x0a2fbf…29b1
4 touches
1 conflict
0xbfe60507…e20a
0x0a2fbf…29b1
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0x0a2fbf2d…f729b1
1 conflict on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity