pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,503,772
← previous block
next block →
recent activity
Analyzing
Block #99,503,772
13 transactions · 11 stateful · 2026-08-27 03:08:43 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,503,772
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
execOrders
#4
execOrders
· blocks 1
#5
0x62be7533
#6
0x3f5c179b
#7
redeemDelegations
· blocks 1
#9
bet
#10
0xed82b078
#12
setData
#8
redeemDelegations
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x8aba370d…aa23
0x34b655…2a6f
4 touches
1 conflict
0xc1b89907…8134
0x34b655…2a6f
4 touches
1 conflict
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x9194f4a3…10b8
0x754704…b603
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
0x72083f0d9f…8e082a
Audit this contract →
← previous block
·
next block →
recent activity