← previous blocknext block →recent activity
Analyzing
Block #89,560,285
19 transactions · 18 stateful · 2026-07-23 03:50:50 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,560,285 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w210w316w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20d0c78a…d1ae
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xdf1a0b65…3582
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x06df379f…2653
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
3 conflicts on slot 0x20d0c78aaa…2ad1ae
Audit this contract →
← previous block·next block →recent activity