pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,436,217
← previous block
next block →
recent activity
Analyzing
Block #73,436,217
10 transactions · 9 stateful · 2026-05-09 10:06:50 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,436,217
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updateDataFeedsValuesPartial
#4
swap
#5
setData
#6
updatePosition
#7
0xed82b078
· blocks 1
#8
0xed82b078
#2
deposit
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4b28162a…a34c
0x754704…b603
2 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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