pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,201,366
← previous block
next block →
recent activity
Analyzing
Block #84,201,366
13 transactions · 11 stateful · 2026-06-28 07:15:10 UTC
Parallelism
77
/100
Blocked
27
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,201,366
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#4
0x6ad2e98b
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x0f6795d9
#9
updatePriceFeedsIfNecessary
#10
0x0f6795d9
#11
0x39435dac
· blocks 1
#2
execute
· blocks 1
#12
0x39435dac
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x24b18e…3301
6 touches
3 conflicts
0x00000000…0001
0x24b18e…3301
6 touches
3 conflicts
0x00000000…0002
0x5f1159…456b
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x5f1159…456b
6 touches
3 conflicts
0x8c902d00…108d
0x754704…b603
6 touches
3 conflicts
0xa743c8dd…ebf2
0x788571…8888
6 touches
3 conflicts
0x5f4d76af…652f
0x788571…8888
6 touches
3 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:
0x24b18eb6…733301
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity