pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,987,194
← previous block
next block →
recent activity
Analyzing
Block #103,987,194
15 transactions · 15 stateful · 2026-09-11 20:09:20 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,987,194
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
0x928e4afa
#6
0x5acec890
#7
0x5acec890
#8
updateDataFeedsValuesPartial
#9
0x59558d29
#10
setData
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
batchUpdatePrice
#14
0x6aa45ff3
#2
swap
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
0x7debb705…4154
0xe700a0…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xa5908184…0fef
0x34b655…2a6f
2 touches
0 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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:
0xe700a02a…bc7777
1 conflict on slot
0x7debb705f9…1c4154
Audit this contract →
← previous block
·
next block →
recent activity