pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,467,879
← previous block
next block →
recent activity
Analyzing
Block #83,467,879
14 transactions · 11 stateful · 2026-06-24 21:44:45 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,467,879
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0xccf50a51
#6
0x1be2fb9c
#7
0x98717539
#8
0x98717539
#10
executeBatch
#11
setData
#12
0x0f6795d9
#13
0x6a3c5045
#9
addBuyOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x0a6e8657…e59d
0x065c9d…c394
2 touches
0 conflicts
0x2aaa7ddf…a76f
0x065c9d…c394
2 touches
0 conflicts
0xb203d40a…e593
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity