pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,491,434
← previous block
next block →
recent activity
Analyzing
Block #73,491,434
9 transactions · 7 stateful · 2026-05-09 16:14:26 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,491,434
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
updateDataFeedsValuesPartial
#4
0xed82b078
#6
0x69ff5dda
#7
setData
#8
relay
#3
0x5339c59f
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28f67b25…ef90
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xceec903a…eb28
0x065c9d…c394
3 touches
1 conflict
0xacb64381…19af
0x065c9d…c394
3 touches
1 conflict
0x32c69a2a…b4ad
0x065c9d…c394
2 touches
0 conflicts
0x4fcb0db8…2b93
0x065c9d…c394
2 touches
0 conflicts
0x72a7135c…ad38
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
0x28f67b252f…57ef90
Audit this contract →
← previous block
·
next block →
recent activity