pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,478,555
← previous block
next block →
recent activity
Analyzing
Block #81,478,555
15 transactions · 8 stateful · 2026-06-15 16:23:34 UTC
Parallelism
87
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,478,555
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
withdraw
#11
updateDataFeedsValuesPartial
#12
0x6a30277d
#13
setData
#14
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00966e54…7d1d
0x34b655…2a6f
2 touches
0 conflicts
0x185301a6…4838
0x34b655…2a6f
2 touches
0 conflicts
0x71641e8d…a781
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:
0x6fae9933…7ba56d
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity