← previous blocknext block →recent activity
Analyzing
Block #89,579,873
10 transactions · 7 stateful · 2026-07-23 06:01:41 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,579,873 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0413d1ed…ad55
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x45d2c7d4…6c36
0x34b655…2a6f
2 touches
0 conflicts
0x46361afb…9d6b
0x34b655…2a6f
2 touches
0 conflicts
0x4e135144…4167
0x34b655…2a6f
2 touches
0 conflicts
0x5fde4971…aac9
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 0x0413d1edab…f8ad55
Audit this contract →
← previous block·next block →recent activity