pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,046,782
← previous block
next block →
recent activity
Analyzing
Block #86,046,782
12 transactions · 9 stateful · 2026-07-06 20:17:12 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,046,782
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
batchUpdate
· blocks 1
#8
0xed82b078
#9
execFwdPositionOps
#10
setData
#11
execOrders
#2
execOrders
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x30fa662a…06e0
0x34b655…2a6f
2 touches
0 conflicts
0x392bf56c…4078
0x34b655…2a6f
2 touches
0 conflicts
0x5229d4af…173b
0x34b655…2a6f
2 touches
0 conflicts
0x6bf91170…3eac
0x34b655…2a6f
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