← previous blocknext block →recent activity
Analyzing
Block #89,384,909
41 transactions · 32 stateful · 2026-07-22 08:19:05 UTC
Parallelism
81/100
Blocked
66%
Avg conflicts / tx
2.02
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,384,909 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w311w412w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x78304d94…9e5e
0x34b655…2a6f
8 touches
6 conflicts
0x5502e1cc…3910
0x34b655…2a6f
8 touches
6 conflicts
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0xa275eacd…6773
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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: 0x48cba278…e2b48b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity