pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,025,748
← previous block
next block →
recent activity
Analyzing
Block #100,025,748
12 transactions · 12 stateful · 2026-08-28 23:10:00 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,025,748
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
execOrders
#4
0x5acec890
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
· blocks 2
#10
0x3f5c179b
#11
execOrders
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9fa93a…f523
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x130d8881…3206
0x34b655…2a6f
2 touches
0 conflicts
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x16d77246…bac5
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
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
1 conflict on slot
0xcc9fa93abb…ddf523
Audit this contract →
← previous block
·
next block →
recent activity