pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,394,816
← previous block
next block →
recent activity
Analyzing
Block #102,394,816
12 transactions · 12 stateful · 2026-09-06 06:12:44 UTC
Parallelism
83
/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,394,816
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0xab083028
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
execFwdPositionOpsV2
· blocks 1
#9
setAccess
#10
0x6a9d045f
#11
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x183d9280…e5ec
0x34b655…2a6f
4 touches
1 conflict
0x643fa4aa…a822
0x754704…b603
2 touches
0 conflicts
0x73bb65fc…650d
0x754704…b603
2 touches
0 conflicts
0xd1eae902…bfd4
0x754704…b603
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
0x5d1ac445db…e05233
Audit this contract →
← previous block
·
next block →
recent activity