pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,318,634
← previous block
next block →
recent activity
Analyzing
Block #73,318,634
7 transactions · 6 stateful · 2026-05-08 21:04:37 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,318,634
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#3
0x000000b2
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#6
setData
#2
0x98717539
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
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0xac8e97a0…8426
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x0c5811ce…dfd8
0x34b655…2a6f
4 touches
1 conflict
0x1319ae2c…7f9a
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
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:
0xc8689a47…62ee79
1 conflict on slot
0xc6417de023…802191
Audit this contract →
← previous block
·
next block →
recent activity