← previous blocknext block →recent activity
Analyzing
Block #89,702,872
9 transactions · 8 stateful · 2026-07-23 18:28:43 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,702,872 · 9 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85d21fba…c8b2
0x34b655…2a6f
4 touches
1 conflict
0x877d236b…65eb
0x34b655…2a6f
4 touches
1 conflict
0x939080d0…59eb
0x34b655…2a6f
4 touches
1 conflict
0x9e85696d…c573
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
1 conflict on slot 0x85d21fba47…9fc8b2
Audit this contract →
← previous block·next block →recent activity