pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,230,168
← previous block
next block →
recent activity
Analyzing
Block #94,230,168
5 transactions · 3 stateful · 2026-08-08 14:33:53 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,230,168
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
placeAndExecuteMarketSell
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#2
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0231b5d…46c4
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xa2478c84…6956
0x754704…b603
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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: Market-MON/USDC
1 conflict on slot
0xe0231b5d96…6246c4
Audit this contract →
← previous block
·
next block →
recent activity