pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,065,173
← previous block
next block →
recent activity
Analyzing
Block #84,065,173
13 transactions · 10 stateful · 2026-06-27 16:08:16 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,065,173
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapWithBackendSignature
· blocks 1
#3
updatePrices
#4
0x98717539
#5
0x0f6795d9
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
0x6a3ff5e8
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#12
0x39435dac
#2
0xeabbe9d8
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6901bef4…4a69
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0002
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…000c
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0009
0x04ddf6…7f33
2 touches
0 conflicts
0xb9a1f6c3…4e41
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:
USDC (USDC)
1 conflict on slot
0x6901bef484…484a69
Audit this contract →
← previous block
·
next block →
recent activity