pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,225,539
← previous block
next block →
recent activity
Analyzing
Block #94,225,539
9 transactions · 8 stateful · 2026-08-08 14:10:25 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,225,539
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xeb282f7f
#2
execFwdPositionOps
#3
placeAndExecuteMarketSell
· blocks 2
#6
updateDataFeedsValuesPartial
#7
0x6a773949
#8
setData
#4
placeAndExecuteMarketBuy
· blocks 1
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x86b42dcd…7dda
0x065c9d…c394
3 touches
1 conflict
0x95d33a02…0802
0x065c9d…c394
3 touches
1 conflict
0x8ef54f25…9166
0x1efe02…37d6
2 touches
0 conflicts
0xb0059330…5947
0x1efe02…37d6
2 touches
0 conflicts
0x0e7d4ad9…3d73
0xea1b8e…c5ec
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
0x0778475bb2…63bd75
Audit this contract →
← previous block
·
next block →
recent activity