← previous blocknext block →recent activity
Analyzing
Block #99,447,946
51 transactions · 42 stateful · 2026-08-26 22:27:38 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.63
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,447,946 · 51 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w08w19w210w011w114w015w117w319w121w123w124w425w526w627w728w833w234w937w141w745w1047w1248w13
- 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
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xe97d54c5…ef6f
0x34b655…2a6f
8 touches
6 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
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