← previous blocknext block →recent activity
Analyzing
Block #89,828,873
32 transactions · 30 stateful · 2026-07-24 05:04:47 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
3.16
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #89,828,873 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w110w011w012w113w214w115w316w417w218w519w621w722w823w324w925w1026w427w528w629w730w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
22 touches
55 conflicts
0x92339d95…0800
0x0000a8…8888
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
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: 0xb1c8ead4…c38888
55 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity