← previous blocknext block →recent activity
Analyzing
Block #89,570,794
13 transactions · 13 stateful · 2026-07-23 05:01:09 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,570,794 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x357773b7…8c0e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x71ac6495…0817
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x9211e33e…0b61
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 0x357773b7b4…b68c0e
Audit this contract →
← previous block·next block →recent activity