pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,859,176
← previous block
next block →
recent activity
Analyzing
Block #99,859,176
9 transactions · 9 stateful · 2026-08-28 09:10:49 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,859,176
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
transferWithAuthorization
#4
setData
#5
approve
#6
execFwdPositionOpsV2
· blocks 1
#8
0x6a915111
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf5fe80…1ffc
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
2 touches
0 conflicts
0x0cadaaea…453a
0x34b655…2a6f
2 touches
0 conflicts
0xd17580f9…ece1
0x754704…b603
2 touches
0 conflicts
0xe9a946e0…2c17
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
0xfaf5fe80ab…a71ffc
Audit this contract →
← previous block
·
next block →
recent activity