pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,398,620
← previous block
next block →
recent activity
Analyzing
Block #93,398,620
15 transactions · 14 stateful · 2026-08-05 16:47:55 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,398,620
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
approve
· blocks 1
#4
matchOrders
#5
execOrders
· blocks 1
#6
updatePrices
#7
0x5acec890
#8
updateDataFeedsValuesPartial
#10
repayWithCollateral
#11
execFwdPositionOps
#12
transfer
#13
setData
#14
0x59558d29
#3
swap
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0xda126ddd…b188
0x3ec731…7777
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe75ca10f…d28a
0x3bd359…433a
2 touches
0 conflicts
0x95e37fef…f5bf
0x3ec731…7777
2 touches
0 conflicts
0x00000000…002e
0x59df86…2780
2 touches
0 conflicts
0x00000000…002f
0x59df86…2780
2 touches
0 conflicts
0x00000000…0030
0x59df86…2780
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
0x428b6e5b99…c18909
Audit this contract →
← previous block
·
next block →
recent activity