← previous blocknext block →recent activity
Analyzing
Block #89,551,396
32 transactions · 29 stateful · 2026-07-23 02:51:32 UTC
Parallelism
63/100
Blocked
66%
Avg conflicts / tx
1.72
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #89,551,396 · 32 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w110w211w312w413w514w515w616w718w120w821w925w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x69d0a300…67ef
0x34b655…2a6f
6 touches
3 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
6 touches
3 conflicts
0xdec4fb9a…1d0c
0x34b655…2a6f
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity