pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,847,746
← previous block
next block →
recent activity
Analyzing
Block #104,847,746
12 transactions · 12 stateful · 2026-09-14 20:55:14 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
#104,847,746
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
approve
#3
approve
#4
approve
#5
approve
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x5acec890
· blocks 1
#9
0x5acec890
#11
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7867a0c…4c51
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x6d955786…1327
0x34b655…2a6f
2 touches
0 conflicts
0x941bd594…21fd
0x34b655…2a6f
2 touches
0 conflicts
0xb6fcbbb7…2b31
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
0xa7867a0ceb…034c51
Audit this contract →
← previous block
·
next block →
recent activity