pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,924,998
← previous block
next block →
recent activity
Analyzing
Block #101,924,998
10 transactions · 9 stateful · 2026-09-04 14:31:28 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,924,998
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
0x000001e4
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
forward
#9
setData
#2
execOrders
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
0x0bb33e3f…7072
0x34b655…2a6f
4 touches
1 conflict
0x08c5d8d8…c7c1
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x61a11641…fef0
0x34b655…2a6f
4 touches
1 conflict
0x7c3ee46f…a8f4
0x34b655…2a6f
4 touches
1 conflict
0xc4f2b9b5…8a71
0x34b655…2a6f
4 touches
1 conflict
0x40a2e73d…5272
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x0bb33e3fc9…697072
Audit this contract →
← previous block
·
next block →
recent activity