pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,897,345
← previous block
next block →
recent activity
Analyzing
Block #74,897,345
10 transactions · 8 stateful · 2026-05-16 04:41:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,897,345
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a07f5fa
#2
0x98717539
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
forward
#6
updateTemporalNumericValuesV1
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x053c0052
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0af68191…1808
0x34b655…2a6f
2 touches
0 conflicts
0x16665060…e752
0x34b655…2a6f
2 touches
0 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
2 touches
0 conflicts
0x2fad73a1…ae09
0x34b655…2a6f
2 touches
0 conflicts
0x35bf0351…9be7
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity