pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,337,328
← previous block
next block →
recent activity
Analyzing
Block #106,337,328
12 transactions · 11 stateful · 2026-09-20 01:54:46 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,337,328
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
matchOrders
#4
execOrders
#5
0x59558d29
#6
0x59558d29
#7
updateDataFeedsValuesPartial
#8
setData
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0x6aaf3ce8
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2daafc8e…0684
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x450e5c00…50d9
0x065c9d…c394
2 touches
0 conflicts
0x5007e668…1685
0x065c9d…c394
2 touches
0 conflicts
0x7c8f0654…8e21
0x065c9d…c394
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x2daafc8ed6…700684
Audit this contract →
← previous block
·
next block →
recent activity