pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,640,286
← previous block
next block →
recent activity
Analyzing
Block #85,640,286
8 transactions · 7 stateful · 2026-07-04 23:06:25 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,640,286
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
setData
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
execFwdPositionOps
#7
0xc7e3ec2c
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xad7485e4…d9d1
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x731c81df…451f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4884fbb0…e3cc
0x065c9d…c394
3 touches
1 conflict
0x5558bcec…d20c
0x065c9d…c394
3 touches
1 conflict
0x84832a16…c4a0
0x065c9d…c394
3 touches
1 conflict
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
0x9ff176a9ad…67152e
Audit this contract →
← previous block
·
next block →
recent activity