← previous blocknext block →recent activity
Analyzing
Block #99,241,540
66 transactions · 46 stateful · 2026-08-26 05:08:35 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.56
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #99,241,540 · 66 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w015w116w220w322w025w126w028w029w130w231w332w033w134w236w138w340w241w456w557w659w860w965w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xb409e204…89ac
0x34b655…2a6f
10 touches
10 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity