pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,063,378
← previous block
next block →
recent activity
Analyzing
Block #84,063,378
13 transactions · 10 stateful · 2026-06-27 15:56:22 UTC
Parallelism
69
/100
Blocked
30
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,063,378
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 3
#5
updatePrices
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
executeBatch
#9
0x0c7abd22
#10
0xed82b078
#11
0x6a3ff31d
#12
setData
#2
updatePrices
· blocks 2
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
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:
0xd637b38f…c64160
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity