← previous blocknext block →recent activity
Analyzing
Block #89,774,308
13 transactions · 13 stateful · 2026-07-24 00:29:28 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,774,308 · 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
2w04w05w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0xaee74ef4…60d5
0x34b655…2a6f
4 touches
1 conflict
0xb6fd0cad…c2b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x1c72cf87…ce1d
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
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
1 conflict on slot 0xef048f923c…1f572b
Audit this contract →
← previous block·next block →recent activity