pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,487,243
← previous block
next block →
recent activity
Analyzing
Block #94,487,243
6 transactions · 5 stateful · 2026-08-09 12:18:26 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,487,243
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
placeAndExecuteMarketSell
· blocks 1
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#2
placeAndExecuteMarketSell
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71162ad1…6931
0x065c9d…c394
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x15ae3bf3…2507
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d5
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d6
0x34b655…2a6f
2 touches
0 conflicts
0x31b06932…8a2e
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: Market-MON/USDC
1 conflict on slot
0x71162ad1e5…586931
Audit this contract →
← previous block
·
next block →
recent activity