← previous blocknext block →recent activity
Analyzing
Block #89,664,451
17 transactions · 16 stateful · 2026-07-23 15:14:11 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,664,451 · 17 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
1w02w03w17w08w19w110w211w313w215w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a7af3fd…72a6
0x34b655…2a6f
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0x88bce118…6a75
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0x252771a6…3918
0x34b655…2a6f
5 touches
3 conflicts
0x6dc9ce62…9b3b
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: Perpl
6 conflicts on slot 0x8a7af3fdbb…2b72a6
Audit this contract →
← previous block·next block →recent activity