pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,237,531
← previous block
next block →
recent activity
Analyzing
Block #109,237,531
15 transactions · 13 stateful · 2026-09-30 05:22:55 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,237,531
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x5acec890
#3
0x3e2e8792
#4
0x5acec890
#5
0x928e4afa
#6
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOpsV2
· blocks 1
#10
0xed82b078
#11
0xed82b078
#12
execFwdPositionOpsV2
#13
setData
#14
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x00c7bbad…fa1b
0x34b655…2a6f
2 touches
0 conflicts
0x2ac147ee…3606
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
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
0x7d9ef2836a…01ddd1
Audit this contract →
← previous block
·
next block →
recent activity