pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,214,834
← previous block
next block →
recent activity
Analyzing
Block #72,214,834
11 transactions · 10 stateful · 2026-05-03 18:28:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,214,834
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
updatePrices
#3
0x9036287a
· blocks 1
#4
0x98717539
#5
collect
#6
updateDataFeedsValuesPartial
#8
forward
#9
setData
#10
0x39435dac
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3542f402…91b6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8e036ae0…1853
0x065c9d…c394
3 touches
1 conflict
0x04a8f1df…9eb5
0x065c9d…c394
2 touches
0 conflicts
0x22293d4e…b01a
0x065c9d…c394
2 touches
0 conflicts
0x298bcc29…3960
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
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
0x3542f40284…e991b6
Audit this contract →
← previous block
·
next block →
recent activity