pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,805,650
← previous block
next block →
recent activity
Analyzing
Block #107,805,650
13 transactions · 8 stateful · 2026-09-25 05:08:40 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,805,650
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updatePosition
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x61d59c2d
· blocks 1
#8
0x61d59c2d
#9
0x61d59c2d
#10
0x61d59c2d
#11
0x61d59c2d
#12
execOrders
#7
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9ca
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xb71f7e11…d40e
0x34ae4d…3fc5
2 touches
0 conflicts
0xe49b1b9b…0be1
0x34ae4d…3fc5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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:
0x508254c8…4a98bd
1 conflict on slot
0x3a663e9a3a…2fa9ca
Audit this contract →
← previous block
·
next block →
recent activity