← previous blocknext block →recent activity
Analyzing
Block #89,757,550
14 transactions · 13 stateful · 2026-07-23 23:04:48 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,757,550 · 14 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
1w02w03w14w06w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x329f2f7d…dcff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x113ca9e4…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x7a2fc410…c088
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x27b96981…ef48
0x34b655…2a6f
4 touches
1 conflict
0x49141cce…8f8f
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
6 conflicts on slot 0x329f2f7d67…aadcff
Audit this contract →
← previous block·next block →recent activity