← previous blocknext block →recent activity
Analyzing
Block #89,545,380
18 transactions · 17 stateful · 2026-07-23 02:11:18 UTC
Parallelism
56/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,545,380 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w19w210w312w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99cc4915…8efa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6a6e42c5…9438
0x34b655…2a6f
6 touches
3 conflicts
0xb900efa2…8624
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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
10 conflicts on slot 0x99cc49159b…eb8efa
Audit this contract →
← previous block·next block →recent activity