← previous blocknext block →recent activity
Analyzing
Block #89,673,894
15 transactions · 13 stateful · 2026-07-23 16:02:23 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,673,894 · 15 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
1w02w16w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd3a70a55…3118
0x065c9d…c394
3 touches
1 conflict
0x08027392…5aa0
0x065c9d…c394
3 touches
1 conflict
0x3527eed0…3e64
0x065c9d…c394
2 touches
0 conflicts
0x39565998…d6bf
0x065c9d…c394
2 touches
0 conflicts
0x170a7604…a391
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity