← previous blocknext block →recent activity
Analyzing
Block #89,542,704
21 transactions · 19 stateful · 2026-07-23 01:53:25 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,542,704 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w310w211w315w416w517w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc458f63a…40d7
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x69d0a300…67ef
0x34b655…2a6f
6 touches
3 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
6 touches
3 conflicts
0x2fcd4130…b4a5
0xc8689a…ee79
4 touches
1 conflict
0x206f4379…e08a
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
15 conflicts on slot 0xc458f63a62…e940d7
Audit this contract →
← previous block·next block →recent activity