pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,038,494
← previous block
next block →
recent activity
Analyzing
Block #73,038,494
10 transactions · 7 stateful · 2026-05-07 14:00:44 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,038,494
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fc9b83
#2
0x69fc9b83
#3
0x121eab2f
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x69fc9b83
#7
0xeffdedb0
#8
setData
#9
execute
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x1446465a…66c5
0x065c9d…c394
4 touches
1 conflict
0x2d57c38b…342f
0x065c9d…c394
3 touches
1 conflict
0x512ec12a…1a6f
0x065c9d…c394
3 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
2 touches
0 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
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