pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,349,883
← previous block
next block →
recent activity
Analyzing
Block #86,349,883
14 transactions · 13 stateful · 2026-07-08 06:00:30 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,349,883
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
#2
0xaf5e395a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
0x62be7533
#7
0x0f6795d9
#8
0x3f5c179b
#9
0x3f5c179b
#10
0x0f6795d9
#11
forward
#13
setData
#12
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd38b5f35…caf1
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x66418872…ac0a
0x0594c7…a3be
2 touches
0 conflicts
0x40e2d65d…2a35
0x3bd359…433a
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
0xd38b5f3503…0fcaf1
Audit this contract →
← previous block
·
next block →
recent activity