← previous blocknext block →recent activity
Analyzing
Block #89,734,889
27 transactions · 23 stateful · 2026-07-23 21:10:19 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,734,889 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w110w211w012w113w215w216w017w119w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity