pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,474,384
← previous block
next block →
recent activity
Analyzing
Block #94,474,384
11 transactions · 10 stateful · 2026-08-09 11:13:46 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,474,384
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0x0c7abd22
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#9
setData
#10
0xc7e3ec2c
#7
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9706989c…c90b
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x52c17a…f6f4
2 touches
0 conflicts
0x27f3e04f…da51
0x52c17a…f6f4
2 touches
0 conflicts
0x87b6f7d3…e811
0x52c17a…f6f4
2 touches
0 conflicts
0x9b3b7500…7817
0x52c17a…f6f4
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
0x9706989cf7…30c90b
Audit this contract →
← previous block
·
next block →
recent activity