← previous blocknext block →recent activity
Analyzing
Block #89,756,621
15 transactions · 14 stateful · 2026-07-23 23:00:07 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,756,621 · 15 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
1w03w04w15w08w09w111w213w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1deed43d…5768
0x34b655…2a6f
4 touches
1 conflict
0x2edb0a6e…06c3
0x34b655…2a6f
4 touches
1 conflict
0x3e644b16…807b
0x34b655…2a6f
4 touches
1 conflict
0x42e08579…09bb
0x34b655…2a6f
4 touches
1 conflict
0x4f999789…32d4
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity