← previous blocknext block →recent activity
Analyzing
Block #89,740,881
6 transactions · 6 stateful · 2026-07-23 21:40:37 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,740,881 · 6 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58d0a23c…5d3a
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x6aea3f64…bb1f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6d11d4a8…3a2d
0x34b655…2a6f
4 touches
1 conflict
0x4deeee1b…8c0c
0x34b655…2a6f
2 touches
0 conflicts
0x5edb8bbe…bc75
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
1 conflict on slot 0x58d0a23cc9…4e5d3a
Audit this contract →
← previous block·next block →recent activity