← previous blocknext block →recent activity
Analyzing
Block #89,674,735
13 transactions · 13 stateful · 2026-07-23 16:06:40 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,674,735 · 13 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
1w02w13w04w15w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x547aca0d…7af0
0x0a2fbf…29b1
6 touches
3 conflicts
0x547aca0d…7af1
0x0a2fbf…29b1
6 touches
3 conflicts
0xe0eb38e4…f8bc
0x0a2fbf…29b1
6 touches
3 conflicts
0xe0eb38e4…f8bd
0x0a2fbf…29b1
6 touches
3 conflicts
0xe0eb38e4…f8c0
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity