← previous blocknext block →recent activity
Analyzing
Block #89,680,184
22 transactions · 19 stateful · 2026-07-23 16:34:19 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,680,184 · 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
4w06w17w28w39w414w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
8 touches
6 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x757057f2…8eed
0x34b655…2a6f
4 touches
1 conflict
0x7fb9cf6f…8778
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 0x8743e1bab8…0a8331
Audit this contract →
← previous block·next block →recent activity