← previous blocknext block →recent activity
Analyzing
Block #89,538,913
18 transactions · 14 stateful · 2026-07-23 01:28:04 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,538,913 · 18 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
4w05w17w09w111w212w213w314w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fbd5ec9…7fb4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1af19f5c…aee2
0x34b655…2a6f
4 touches
1 conflict
0x539ecb5b…871b
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x6af385b8…971b
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 0x6fbd5ec97b…267fb4
Audit this contract →
← previous block·next block →recent activity