← previous blocknext block →recent activity
Analyzing
Block #89,667,863
30 transactions · 25 stateful · 2026-07-23 15:31:32 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,667,863 · 30 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
2w03w04w05w112w013w114w215w316w417w118w119w222w123w224w227w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x94ddea60…a24d
0x34b655…2a6f
4 touches
1 conflict
0xad95efd9…b4cf
0x34b655…2a6f
4 touches
1 conflict
0xc95ff3cf…26cc
0x34b655…2a6f
4 touches
1 conflict
0xe684760e…ece0
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity