← previous blocknext block →recent activity
Analyzing
Block #89,675,419
17 transactions · 16 stateful · 2026-07-23 16:10:10 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,675,419 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x8f450e8e…11c7
0x34b655…2a6f
4 touches
1 conflict
0xb733b9da…9c31
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7ae4938b…f4f3
0x34b655…2a6f
4 touches
1 conflict
0xfe8a0311…1ba7
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
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 0xda27c76455…2e7fab
Audit this contract →
← previous block·next block →recent activity