pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,278,503
← previous block
next block →
recent activity
Analyzing
Block #99,278,503
11 transactions · 11 stateful · 2026-08-26 08:14:37 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,278,503
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
· blocks 1
#5
0x57368ddf
#6
execFwdPositionOpsV2
#7
transfer
#8
0x6a8ea0e4
#9
setData
#10
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x067d9d94…af26
0x34b655…2a6f
2 touches
0 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x13d12d78…4c97
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x295780b7…d2d1
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:
Perpl
1 conflict on slot
0xbd590df7f7…cf9891
Audit this contract →
← previous block
·
next block →
recent activity