← previous blocknext block →recent activity
Analyzing
Block #89,570,952
13 transactions · 12 stateful · 2026-07-23 05:02:12 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,570,952 · 13 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
1w02w13w25w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2c58246…1537
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x20497f5e…c503
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x520e8f05…92ef
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 0xb2c58246a5…511537
Audit this contract →
← previous block·next block →recent activity