pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,917,715
← previous block
next block →
recent activity
Analyzing
Block #73,917,715
8 transactions · 8 stateful · 2026-05-11 15:47:44 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,917,715
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#2
0x1ffa3c9b
· blocks 2
#3
0x1ffa3c9b
· blocks 1
#4
0x1ffa3c9b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x6b319071…a105
0xc8689a…ee79
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x1a4b4152…0a08
0x5d823e…89c6
6 touches
3 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x5d823e…89c6
6 touches
3 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
6 conflicts on slot
0xf537eaa0c6…3873c8
Audit this contract →
← previous block
·
next block →
recent activity