← previous blocknext block →recent activity
Analyzing
Block #89,537,964
25 transactions · 23 stateful · 2026-07-23 01:21:43 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,537,964 · 25 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
3w04w15w26w38w09w110w013w014w216w317w119w020w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x405da62e…192a
0xa6afd3…d132
8 touches
6 conflicts
0xb476ee35…c627
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x06fc4ae9…8548
0xa6afd3…d132
5 touches
3 conflicts
0x098e8043…958c
0x34b655…2a6f
4 touches
1 conflict
0x2debe664…1818
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