← previous blocknext block →recent activity
Analyzing
Block #99,477,470
34 transactions · 30 stateful · 2026-08-27 00:56:16 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.65
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,477,470 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w08w111w113w114w218w320w421w522w324w425w528w631w733w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xe6c7c1ac…6305
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xa77dd907…4cb5
0x34b655…2a6f
8 touches
6 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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: Perpl
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity