pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,372,405
← previous block
next block →
recent activity
Analyzing
Block #94,372,405
11 transactions · 9 stateful · 2026-08-09 02:35:58 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,372,405
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
placeAndExecuteMarketBuy
· blocks 2
#6
forward
#7
forward
#8
0xed82b078
#9
updateDataFeedsValuesPartial
#10
0x39435dac
#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
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x6e7bb7b2…df82
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xa85e1f81…c3ff
0x065c9d…c394
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9e
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa0
0x2b46c0…1669
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
3 conflicts on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity