pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,816,910
← previous block
next block →
recent activity
Analyzing
Block #107,816,910
11 transactions · 11 stateful · 2026-09-25 06:05:20 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,816,910
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0x5acec890
#3
forward
#4
0x84403c1b
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
transfer
#8
0x61d59c2d
· blocks 2
#9
0x61d59c2d
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a18f58…4cff
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x232b0b19…d946
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x63c421ca…8cde
0x34b655…2a6f
2 touches
0 conflicts
0x93ef58a2…0c61
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:
0x508254c8…4a98bd
1 conflict on slot
0x34a18f581d…e94cff
Audit this contract →
← previous block
·
next block →
recent activity