pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,971,019
← previous block
next block →
recent activity
Analyzing
Block #94,971,019
14 transactions · 12 stateful · 2026-08-11 04:53:12 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,971,019
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x8263f5d9
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
0x3f5c179b
#9
0x94defb17
· blocks 1
#11
0x0f6795d9
#12
setData
#13
0x39435dac
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0002d653…52ea
0x968279…9342
4 touches
1 conflict
0x0002d653…52ed
0x968279…9342
4 touches
1 conflict
0x0002d653…52ee
0x968279…9342
4 touches
1 conflict
0x0002d653…52f0
0x968279…9342
4 touches
1 conflict
0xcfcf38b9…18d6
0x968279…9342
4 touches
1 conflict
0xcfcf38b9…18d7
0x968279…9342
4 touches
1 conflict
0xcfcf38b9…18d9
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0x0002d65352…4f52ea
Audit this contract →
← previous block
·
next block →
recent activity