← previous blocknext block →recent activity
Analyzing
Block #89,596,804
21 transactions · 21 stateful · 2026-07-23 07:54:46 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,596,804 · 21 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
1w02w13w24w05w16w09w010w111w212w313w415w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x06d44196…338c
0x0a2fbf…29b1
10 touches
10 conflicts
0x06d44196…338d
0x0a2fbf…29b1
10 touches
10 conflicts
0x06d44196…3390
0x0a2fbf…29b1
10 touches
10 conflicts
0xafe1c27e…a7fd
0x0a2fbf…29b1
10 touches
10 conflicts
0xafe1c27e…a7fe
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity