pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,591,243
← previous block
next block →
recent activity
Analyzing
Block #71,591,243
12 transactions · 10 stateful · 2026-04-30 21:14:30 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,591,243
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
addLiquidity
#3
0xeffdedb0
#4
0x1a945f9c
#5
0x9036287a
· blocks 1
#6
updateDataFeedsValuesPartial
#8
0x0c7abd22
#9
0x69f3c6ad
#10
setData
#11
0xb3febd…5b6d
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfb407e…fb3e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3d102245…98f6
0x065c9d…c394
3 touches
1 conflict
0xf013b3df…adff
0x065c9d…c394
3 touches
1 conflict
0x1767f56b…e359
0x065c9d…c394
3 touches
1 conflict
0xb98b9e9d…a785
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x40956391…a8e4
0x5afd3e…7620
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
0x4bfb407ec5…5efb3e
Audit this contract →
← previous block
·
next block →
recent activity