← previous blocknext block →recent activity
Analyzing
Block #89,711,577
17 transactions · 16 stateful · 2026-07-23 19:12:36 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,711,577 · 17 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
2w03w14w28w29w310w411w312w515w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
6 touches
3 conflicts
0x534b7117…f82c
0x34b655…2a6f
4 touches
1 conflict
0x56aee538…6f1f
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity