pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,053,547
← previous block
next block →
recent activity
Analyzing
Block #102,053,547
12 transactions · 12 stateful · 2026-09-05 01:23:10 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
#102,053,547
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#3
updatePrices
#4
execOrders
#5
0x5acec890
#6
0x928e4afa
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#10
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w0
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8799a0d…7136
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0x3d408a46…8a53
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xd2fb0612…5edf
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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
0xd8799a0df0…a17136
Audit this contract →
← previous block
·
next block →
recent activity