← previous blocknext block →recent activity
Analyzing
Block #89,694,721
13 transactions · 13 stateful · 2026-07-23 17:47:41 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,694,721 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w18w310w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x465ce74f…39c8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x57e95ab1…d5ef
0x34b655…2a6f
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
0x4a8ecf20…9c19
0x34b655…2a6f
4 touches
1 conflict
0x529e53cf…38e4
0xa6afd3…d132
4 touches
1 conflict
0x690f65fc…d842
0xa6afd3…d132
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 0x465ce74fea…db39c8
Audit this contract →
← previous block·next block →recent activity