pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,470,783
← previous block
next block →
recent activity
Analyzing
Block #76,470,783
11 transactions · 8 stateful · 2026-05-23 11:45:26 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,470,783
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
updatePosition
#8
setData
#9
0x034e4501
#10
execOrders
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dff7a33…6932
0x065c9d…c394
2 touches
0 conflicts
0x0f1a8001…d063
0x065c9d…c394
2 touches
0 conflicts
0x16eae992…a9fa
0x065c9d…c394
2 touches
0 conflicts
0x78f466ef…7b88
0x065c9d…c394
2 touches
0 conflicts
0xd143ea40…2341
0x065c9d…c394
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity