pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,967,414
← previous block
next block →
recent activity
Analyzing
Block #101,967,414
13 transactions · 13 stateful · 2026-09-04 18:06:40 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,967,414
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xa96df62f
#3
0x5acec890
#4
0x59558d29
#5
execOrders
#7
0x000000b2
· blocks 1
#8
redeemDelegations
#9
execFwdPositionOpsV2
#10
setData
#12
execOrders
#6
0x0c7abd22
#11
0x000000b2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac96109…3059
0x405b63…7777
4 touches
1 conflict
0x00000000…0000
0x24bf77…906e
4 touches
1 conflict
0x00000000…0003
0x24bf77…906e
4 touches
1 conflict
0xc9190cc1…8088
0x3bd359…433a
4 touches
1 conflict
0x0e4d8cb0…61dd
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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:
0x405b6330…827777
1 conflict on slot
0x9ac9610971…c93059
Audit this contract →
← previous block
·
next block →
recent activity