pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,063,819
← previous block
next block →
recent activity
Analyzing
Block #102,063,819
13 transactions · 13 stateful · 2026-09-05 02:15:13 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,063,819
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
0x5acec890
#8
0x5acec890
#9
0x59558d29
#10
executeBatch
#11
setData
#12
execFwdPositionOpsV2
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x7c216fca…20cb
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
0x34b655…2a6f
4 touches
1 conflict
0x898a08aa…c855
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x987859be…2686
0x34b655…2a6f
4 touches
1 conflict
0x999c658d…b185
0x34b655…2a6f
4 touches
1 conflict
0xd98afa6e…3364
0x34b655…2a6f
4 touches
1 conflict
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
0x013150720a…500e2d
Audit this contract →
← previous block
·
next block →
recent activity