pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,746,904
← previous block
next block →
recent activity
Analyzing
Block #85,746,904
11 transactions · 8 stateful · 2026-07-05 10:57:44 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
#85,746,904
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0xbb5dee…906d
#4
execFwdPositionOps
#5
execOrders
#7
0xed82b078
#8
0x6a4a3920
#9
setData
#10
0x9de3bf…bb78
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ee7744e…8ddc
0x065c9d…c394
2 touches
0 conflicts
0x3d1fca16…d653
0x065c9d…c394
2 touches
0 conflicts
0x4c17589f…b30a
0x065c9d…c394
2 touches
0 conflicts
0x5503dd8a…f3f4
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
0x731e6d8269…072883
Audit this contract →
← previous block
·
next block →
recent activity