← previous blocknext block →recent activity
Analyzing
Block #89,377,776
26 transactions · 21 stateful · 2026-07-22 07:31:24 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,377,776 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w110w013w115w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0xdecc4607…097d
0xd32edf…ff58
5 touches
3 conflicts
0x01ceb5de…11f2
0x0a2fbf…29b1
4 touches
1 conflict
0x01ceb5de…11f5
0x0a2fbf…29b1
4 touches
1 conflict
0x54ba126e…dbd0
0x0a2fbf…29b1
4 touches
1 conflict
0x54ba126e…dbd1
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity