← previous blocknext block →recent activity
Analyzing
Block #89,573,257
14 transactions · 14 stateful · 2026-07-23 05:17:33 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,573,257 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w49w110w513w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41cda5c2…5d3f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6c0349d…05b0
0x34b655…2a6f
8 touches
6 conflicts
0x0110331c…b891
0x34b655…2a6f
6 touches
3 conflicts
0x9211e33e…0b61
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9db3090e…7fb8
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
10 conflicts on slot 0x41cda5c22a…945d3f
Audit this contract →
← previous block·next block →recent activity