← previous blocknext block →recent activity
Analyzing
Block #89,873,034
15 transactions · 14 stateful · 2026-07-24 08:47:13 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,873,034 · 15 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
2w03w04w17w28w39w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc49bb0aa…12b1
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc4e28bdd…4cc3
0x34b655…2a6f
6 touches
3 conflicts
0x4c770fe0…b972
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x714a26…182d
6 touches
3 conflicts
0x00000000…0001
0x714a26…182d
6 touches
3 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: Perpl
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity