← previous blocknext block →recent activity
Analyzing
Block #89,769,384
33 transactions · 25 stateful · 2026-07-24 00:04:36 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,769,384 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w112w013w114w215w316w417w519w220w328w131w332w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5a6864fe…2890
0x34b655…2a6f
4 touches
1 conflict
0x5bed55c2…f588
0x34b655…2a6f
4 touches
1 conflict
0x5dd18eb2…4d66
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity