← previous blocknext block →recent activity
Analyzing
Block #89,586,039
15 transactions · 14 stateful · 2026-07-23 06:42:52 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,586,039 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w19w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588380ee…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x20081203…b191
0x34b655…2a6f
4 touches
1 conflict
0x2d3d5254…7c98
0x34b655…2a6f
4 touches
1 conflict
0x4e089204…52fb
0x34b655…2a6f
4 touches
1 conflict
0x4e089204…52fc
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
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 0x588380ee30…d00a5c
Audit this contract →
← previous block·next block →recent activity