pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,152,825
← previous block
next block →
recent activity
Analyzing
Block #100,152,825
10 transactions · 8 stateful · 2026-08-29 09:49:54 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,152,825
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
withdraw
#4
exactInputSingle
#5
setData
#6
execFwdPositionOpsV2
· blocks 2
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x04019a08…3a1f
0x34b655…2a6f
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity