← previous blocknext block →recent activity
Analyzing
Block #89,536,429
9 transactions · 8 stateful · 2026-07-23 01:11:27 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,536,429 · 9 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x268f1193…796b
0x34b655…2a6f
2 touches
0 conflicts
0x2bac71c3…3296
0x34b655…2a6f
2 touches
0 conflicts
0x2e089e16…3614
0x34b655…2a6f
2 touches
0 conflicts
0x3f32c417…7c66
0x34b655…2a6f
2 touches
0 conflicts
0x417a19aa…bb21
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity