pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,060,183
← previous block
next block →
recent activity
Analyzing
Block #94,060,183
11 transactions · 9 stateful · 2026-08-08 00:14:34 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,060,183
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
placeAndExecuteMarketBuy
· blocks 1
#6
updateDataFeedsValuesPartial
#7
commit
#8
0x6a767562
#9
approve
#10
setData
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x10f18761…8e0c
0x34b655…2a6f
2 touches
0 conflicts
0x25e6f91a…a6a4
0x34b655…2a6f
2 touches
0 conflicts
0x323266ad…ee60
0x34b655…2a6f
2 touches
0 conflicts
0x324d7370…8b59
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
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity