pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,652,090
← previous block
next block →
recent activity
Analyzing
Block #73,652,090
8 transactions · 8 stateful · 2026-05-10 10:05:13 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,652,090
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
0x6a0058d0
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x98717539
#7
setData
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7c30918d…f24e
0x065c9d…c394
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
2 touches
0 conflicts
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x1c5f861c…787f
0x34b655…2a6f
2 touches
0 conflicts
0x38524fae…9deb
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xb159af880b…47a9e7
Audit this contract →
← previous block
·
next block →
recent activity