← previous blocknext block →recent activity
Analyzing
Block #89,693,292
10 transactions · 9 stateful · 2026-07-23 17:40:28 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,693,292 · 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
3w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46572d7b…72a3
0x34b655…2a6f
4 touches
1 conflict
0x46572d7b…72a4
0x34b655…2a6f
4 touches
1 conflict
0x7df77211…2dff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9c2c7236…d9c8
0x34b655…2a6f
4 touches
1 conflict
0xad819428…79af
0x34b655…2a6f
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
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 0x46572d7bb7…9672a3
Audit this contract →
← previous block·next block →recent activity