pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,970,784
← previous block
next block →
recent activity
Analyzing
Block #73,970,784
10 transactions · 9 stateful · 2026-05-11 21:40:49 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,970,784
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x98717539
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#2
0x0c7abd22
#5
0x6df9e92b
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0x00000000…0001
0x776059…1d8d
4 touches
1 conflict
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x51750603…1f93
0x065c9d…c394
4 touches
1 conflict
0x6062b9d1…6172
0x065c9d…c394
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:
0xde22b2d5…9f7777
1 conflict on slot
0x9b1a47c3d7…c169f8
Audit this contract →
← previous block
·
next block →
recent activity