pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,442,473
← previous block
next block →
recent activity
Analyzing
Block #74,442,473
11 transactions · 11 stateful · 2026-05-14 02:01:26 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,442,473
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
addSellOrder
· blocks 2
#4
updateDataFeedsValuesPartial
#5
multicall
#6
setData
#7
redeemDelegations
#10
execOrders
#3
0xed82b078
· blocks 2
#8
0xed82b078
#9
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x73eff103…88e7
0x065c9d…c394
3 touches
1 conflict
0xf0be32fd…22cd
0x065c9d…c394
3 touches
1 conflict
0x7f975651…8c28
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x113b3a26…4a92
0x065c9d…c394
2 touches
0 conflicts
0x9d1a81bd…344a
0x065c9d…c394
2 touches
0 conflicts
0xecb6c48f…f8ab
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity