pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,089,936
← previous block
next block →
recent activity
Analyzing
Block #76,089,936
10 transactions · 7 stateful · 2026-05-21 17:29:19 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,089,936
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#4
0x0c7abd22
#5
0xb9bbd3ee
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#2
batchUpdate
#3
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xfcfed5ae…c9ce
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x19e38fcd…7985
0x065c9d…c394
2 touches
0 conflicts
0x8ce9d3b7…d82b
0x065c9d…c394
2 touches
0 conflicts
0x95c5e6ba…45c4
0x065c9d…c394
2 touches
0 conflicts
0xe4e6243c…623d
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xfe2bac2b2f…482cec
Audit this contract →
← previous block
·
next block →
recent activity