pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,750,664
← previous block
next block →
recent activity
Analyzing
Block #93,750,664
11 transactions · 10 stateful · 2026-08-06 22:17:42 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
#93,750,664
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
0x5acec890
#3
execFwdPositionOps
#4
updatePriceFeedsIfNecessary
#5
placeAndExecuteMarketSell
· blocks 1
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xc7e3ec2c
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0x240c7189…b4a6
0x40c49f…2af0
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x34b25521…2ca5
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x4147b177…c9ba
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
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: MarginAccount
1 conflict on slot
0x6518075e89…5f2b17
Audit this contract →
← previous block
·
next block →
recent activity