← previous blocknext block →recent activity
Analyzing
Block #89,526,334
19 transactions · 18 stateful · 2026-07-23 00:04:10 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,526,334 · 19 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
1w02w13w24w08w19w010w111w212w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x344eea7a…886d
0x0a2fbf…29b1
4 touches
1 conflict
0x344eea7a…886e
0x0a2fbf…29b1
4 touches
1 conflict
0x344eea7a…8871
0x0a2fbf…29b1
4 touches
1 conflict
0xaa8a6247…3eb3
0x0a2fbf…29b1
4 touches
1 conflict
0xaa8a6247…3eb4
0x0a2fbf…29b1
4 touches
1 conflict
0xaa8a6247…3eb5
0x0a2fbf…29b1
4 touches
1 conflict
0x155e52ca…fac7
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity