← previous blocknext block →recent activity
Analyzing
Block #89,585,609
19 transactions · 15 stateful · 2026-07-23 06:40:00 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,585,609 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w29w313w014w216w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x45906f00…7177
0x34b655…2a6f
6 touches
3 conflicts
0xcf8e8419…c691
0x34b655…2a6f
6 touches
3 conflicts
0x30871fa4…1eba
0x34b655…2a6f
4 touches
1 conflict
0x5b39147b…cb75
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
0x34b655…2a6f
4 touches
1 conflict
0x9363abeb…c694
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity