← previous blocknext block →recent activity
Analyzing
Block #89,677,588
8 transactions · 7 stateful · 2026-07-23 16:21:14 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,677,588 · 8 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
1w02w13w24w36w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a47a02…d364
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x10b7971b…3ba4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad05
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad06
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad15
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 0xb5a47a02cd…bfd364
Audit this contract →
← previous block·next block →recent activity