← previous blocknext block →recent activity
Analyzing
Block #89,544,390
19 transactions · 16 stateful · 2026-07-23 02:04:41 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,544,390 · 19 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
1w02w04w17w19w210w211w213w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a2c248…f7ed
0x34b655…2a6f
6 touches
3 conflicts
0x7d02a2c5…9802
0x34b655…2a6f
6 touches
3 conflicts
0x434010de…83fe
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x28c714d9…9438
0xa6afd3…d132
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x34a2c24806…f4f7ed
Audit this contract →
← previous block·next block →recent activity