pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,189,912
← previous block
next block →
recent activity
Analyzing
Block #102,189,912
12 transactions · 11 stateful · 2026-09-05 12:54:34 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,189,912
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#3
0x59558d29
#4
updateDataFeedsValuesPartial
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
forward
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0x550382…620b
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x07b76e1f…a8f8
0x34b655…2a6f
2 touches
0 conflicts
0x27826bde…1da4
0x34b655…2a6f
2 touches
0 conflicts
0x5b8c24d0…86c9
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity