pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,353,949
← previous block
next block →
recent activity
Analyzing
Block #84,353,949
12 transactions · 8 stateful · 2026-06-29 00:11:57 UTC
Parallelism
83
/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,353,949
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x5bf9264c
· blocks 1
#5
executeBatch
#6
0x0f6795d9
#7
0x6a41b8c5
#8
setData
#9
0xf0aee1…a19a
#10
0xe5c045…be32
#11
0x39435dac
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
2 touches
0 conflicts
0x5149ba0e…d954
0x754704…b603
2 touches
0 conflicts
0x00000000…0002
0xd637b3…4160
2 touches
0 conflicts
0x04c8137b…e776
0xe52b14…7230
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity