← previous blocknext block →recent activity
Analyzing
Block #89,858,888
29 transactions · 21 stateful · 2026-07-24 07:36:04 UTC
Parallelism
76/100
Blocked
62%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,858,888 · 29 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
1w03w14w05w16w27w38w49w510w011w117w018w119w220w321w425w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x6847107a…f468
0xa6afd3…d132
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0x55012d1a…3907
0x2b46c0…1669
8 touches
6 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
8 touches
6 conflicts
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity