← previous blocknext block →recent activity
Analyzing
Block #89,527,081
23 transactions · 21 stateful · 2026-07-23 00:09:09 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,527,081 · 23 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
1w02w13w26w07w19w210w212w214w316w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf609f09b…f03a
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x78255c70…2734
0x34b655…2a6f
4 touches
1 conflict
0x7c4e3e24…7073
0x34b655…2a6f
4 touches
1 conflict
0x7f06125e…4bb7
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity