pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,841,303
← previous block
next block →
recent activity
Analyzing
Block #101,841,303
11 transactions · 11 stateful · 2026-09-04 07:29:05 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,841,303
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3e2e8792
#2
updatePrices
#3
0x59558d29
#4
execute
#5
batchRequestPriceCallback
#6
0x14bad976
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
execOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
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
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x28b01e5f…ced5
0x2880ab…7b43
2 touches
0 conflicts
0x28b01e5f…ced6
0x2880ab…7b43
2 touches
0 conflicts
0x75065364…d4f9
0x2880ab…7b43
2 touches
0 conflicts
0x75065364…d4fa
0x2880ab…7b43
2 touches
0 conflicts
0x277d2354…4b5c
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