pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#78,363,734
← previous block
next block →
recent activity
Analyzing
Block #78,363,734
13 transactions · 9 stateful · 2026-06-01 06:03:06 UTC
Parallelism
77
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#78,363,734
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a1d2112
#6
setData
#7
execFwdPositionOps
#8
0x6a1d2112
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#2
deposit
· blocks 1
#3
addBuyOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261e21f6…435e
0x2a68ba…90c5
2 touches
1 conflict
0xc3174a06…6a8b
0x754704…b603
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x444db562…4b0a
0x065c9d…c394
2 touches
0 conflicts
0xcad1d335…fea5
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
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
0x261e21f6d4…56435e
Audit this contract →
← previous block
·
next block →
recent activity