← previous blocknext block →recent activity
Analyzing
Block #89,526,320
22 transactions · 21 stateful · 2026-07-23 00:04:04 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,526,320 · 22 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
5w06w19w010w211w315w316w419w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae1101fb…0e7f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0x76641f35…47af
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xae1101fb67…650e7f
Audit this contract →
← previous block·next block →recent activity