pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,474,927
← previous block
next block →
recent activity
Analyzing
Block #99,474,927
10 transactions · 10 stateful · 2026-08-27 00:43:28 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,474,927
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 2
#4
0x59558d29
#5
executeBatch
#7
redeemDelegations
#8
setData
#3
0x5acec890
#6
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3a1c8178…ebbd
0x34b655…2a6f
4 touches
1 conflict
0x498ed94c…967d
0x34b655…2a6f
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0xb55a7cbc…68f5
0x2b46c0…1669
2 touches
0 conflicts
0xbbca528a…1b10
0x2b46c0…1669
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity