pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,349,113
← previous block
next block →
recent activity
Analyzing
Block #73,349,113
8 transactions · 7 stateful · 2026-05-09 00:27:21 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,349,113
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#6
setData
#7
0x39435dac
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bfc28d2…66cb
0x065c9d…c394
2 touches
0 conflicts
0x18e88ff0…bd2d
0x065c9d…c394
2 touches
0 conflicts
0x3e184833…d237
0x065c9d…c394
2 touches
0 conflicts
0xa295e8d1…5a55
0x065c9d…c394
2 touches
0 conflicts
0xa49a7f1d…56bc
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity