← previous blocknext block →recent activity
Analyzing
Block #89,867,216
22 transactions · 22 stateful · 2026-07-24 08:17:58 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,867,216 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w114w015w016w117w118w219w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
10 touches
10 conflicts
0x92339d95…0800
0xb1c8ea…8888
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xeb624d97…2e39
0xe52b14…7230
3 touches
1 conflict
0xc7ea2751…3347
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
10 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity