← previous blocknext block →recent activity
Analyzing
Block #89,752,331
9 transactions · 8 stateful · 2026-07-23 22:38:29 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,752,331 · 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
1w02w14w25w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f28eb14…e5ef
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xfa3848f5…98ee
0x34b655…2a6f
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x4d1a2d8e…9672
0x34b655…2a6f
2 touches
0 conflicts
0x59dccbd8…2bf6
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 0x6f28eb14f4…68e5ef
Audit this contract →
← previous block·next block →recent activity