pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,196,059
← previous block
next block →
recent activity
Analyzing
Block #94,196,059
10 transactions · 8 stateful · 2026-08-08 11:41:09 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,196,059
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 1
#3
0x5acec890
#4
placeAndExecuteMarketBuy
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#9
setData
#5
execFwdPositionOps
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0xcad1ac02…2874
0x065c9d…c394
3 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x28e5dbea…2f7f
0x34b655…2a6f
2 touches
0 conflicts
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x4d8c59fa…944f
0x34b655…2a6f
2 touches
0 conflicts
0x71ac6495…0817
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity