pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,088,339
← previous block
next block →
recent activity
Analyzing
Block #95,088,339
14 transactions · 14 stateful · 2026-08-11 14:44:09 UTC
Parallelism
86
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,088,339
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x0c7abd22
#4
execOrders
· blocks 1
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOps
#10
forward
#11
0x6a7b35b0
#12
transfer
#13
setData
#2
matchOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dbb0f3e…2028
0x99c7a7…8bf0
4 touches
1 conflict
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xef712f4a…0853
0x99c7a7…8bf0
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x8986dd15…1112
0x8f415d…5241
3 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x4dbb0f3e0c…b12028
Audit this contract →
← previous block
·
next block →
recent activity