pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,360,123
← previous block
next block →
recent activity
Analyzing
Block #84,360,123
13 transactions · 8 stateful · 2026-06-29 00:53:10 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,360,123
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x39435dac
#6
0x6a41c26e
#7
setData
#8
0x9047a0…8e18
#9
0xbe7ada…b798
#10
0x39435dac
#11
0x39435dac
#12
0x6a41c26e
#2
updatePrices
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
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x137a69a8…8b93
0x34b655…2a6f
2 touches
0 conflicts
0x2f8f103b…29f4
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
0xd637b38f…c64160
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity