pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,163,979
← previous block
next block →
recent activity
Analyzing
Block #99,163,979
12 transactions · 10 stateful · 2026-08-25 22:38:21 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,163,979
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3fb17519
#2
swap
#3
approve
· blocks 1
#5
execOrders
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x5acec890
· blocks 1
#10
setData
#11
execFwdPositionOpsV2
#4
swap
#6
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe701a042…5f1e
0x15a894…7777
2 touches
1 conflict
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
2 touches
0 conflicts
0xfd6184ca…970c
0x15a894…7777
2 touches
0 conflicts
0x388d69c4…4288
0x188d58…ea8e
2 touches
0 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
2 touches
0 conflicts
0xd9a7cef1…1ed5
0x188d58…ea8e
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
0x89ac61bf64…6b9443
Audit this contract →
← previous block
·
next block →
recent activity