pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,651,981
← previous block
next block →
recent activity
Analyzing
Block #73,651,981
8 transactions · 7 stateful · 2026-05-10 10:04:29 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,651,981
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 1
#4
0x62be7533
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1855675d…3701
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x81955a0a…29ee
0x6657d1…8ccc
2 touches
0 conflicts
0x9a11ce68…4b64
0x6657d1…8ccc
2 touches
0 conflicts
0xeeb8b7fc…24d6
0x6657d1…8ccc
2 touches
0 conflicts
0x0caac6df…b6f9
0x754704…b603
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
0x1855675df6…4a3701
Audit this contract →
← previous block
·
next block →
recent activity