pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,793,148
← previous block
next block →
recent activity
Analyzing
Block #85,793,148
12 transactions · 9 stateful · 2026-07-05 16:05:37 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,793,148
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
addLiquidity
#4
0x0c7abd22
· blocks 1
#6
execFwdPositionOps
#7
setData
#8
0x3a58d4…8adb
#9
execOrders
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#5
batchUpdate
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
0xe1cc89ed…4aac
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x170fec06…3995
0x065c9d…c394
3 touches
1 conflict
0x32a751e4…82d4
0x065c9d…c394
3 touches
1 conflict
0xc5982a5c…012a
0x065c9d…c394
3 touches
1 conflict
0xb88785d1…2309
0x40c49f…2af0
2 touches
0 conflicts
0xdb585e4b…55f4
0x40c49f…2af0
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
0xe1cc89edae…934aac
Audit this contract →
← previous block
·
next block →
recent activity