← previous blocknext block →recent activity
Analyzing
Block #89,696,023
12 transactions · 12 stateful · 2026-07-23 17:54:14 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,696,023 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0xad631952…e126
0x34b655…2a6f
6 touches
3 conflicts
0x46572d7b…72a3
0x34b655…2a6f
4 touches
1 conflict
0x0de2686a…2f69
0x34b655…2a6f
4 touches
1 conflict
0x46572d7b…72a4
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
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 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity