pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,731
← previous block
next block →
recent activity
Analyzing
Block #74,789,731
12 transactions · 10 stateful · 2026-05-15 16:43:56 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,731
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#5
0x62be7533
#9
0x6a074dc3
#10
setData
#11
execOrders
#6
0x0c7abd22
· blocks 2
#7
0xed82b078
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x5aa25a63…dbd7
0x065c9d…c394
4 touches
1 conflict
0x3bb3784c…8d77
0x065c9d…c394
3 touches
1 conflict
0x625587d9…b1ec
0x065c9d…c394
3 touches
1 conflict
0x5197a498…9abe
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity