pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,527,830
← previous block
next block →
recent activity
Analyzing
Block #74,527,830
12 transactions · 10 stateful · 2026-05-14 11:31:35 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,527,830
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a05b30f
#2
0x1ffa3c9b
· blocks 1
#3
updatePrices
· blocks 2
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a05b30f
#10
setData
#11
execOrders
#4
updatePrices
· blocks 1
#6
0x0c7abd22
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w2
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x2a14f23b…ca21
0x065c9d…c394
2 touches
0 conflicts
0x61cb3937…e836
0x065c9d…c394
2 touches
0 conflicts
0x8cab3567…cac1
0x065c9d…c394
2 touches
0 conflicts
0xa7477eac…c855
0x065c9d…c394
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:
0xab35264b…1cfa38
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity