pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,230,171
← previous block
next block →
recent activity
Analyzing
Block #102,230,171
10 transactions · 10 stateful · 2026-09-05 16:18:26 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,230,171
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
0x6a9c40d5
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca544518…82c2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x02372d42…1871
0x34b655…2a6f
2 touches
0 conflicts
0x0561ed30…4ea4
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x14101b3d…913e
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
0xca54451874…2982c2
Audit this contract →
← previous block
·
next block →
recent activity