pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,064,043
← previous block
next block →
recent activity
Analyzing
Block #102,064,043
10 transactions · 9 stateful · 2026-09-05 02:16:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,064,043
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrder
#3
0x0c7abd22
#4
execOrder
#5
0x59558d29
#6
updateDataFeedsValuesPartial
#7
setData
#8
execFwdPositionOpsV2
#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
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00db26c9…af6b
0x34b655…2a6f
2 touches
0 conflicts
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x04ad10af…d599
0x34b655…2a6f
2 touches
0 conflicts
0x0f0e49ae…c1a5
0x34b655…2a6f
2 touches
0 conflicts
0x1dc71894…1884
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity