pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,655,005
← previous block
next block →
recent activity
Analyzing
Block #73,655,005
10 transactions · 7 stateful · 2026-05-10 10:24:55 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,655,005
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a005d6e
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x98717539
· blocks 1
#7
0x6a005d6e
#8
0x6a005d6e
#9
0x39435dac
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23951077…539b
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ac31945…2c72
0x065c9d…c394
2 touches
0 conflicts
0x109e7b87…d0f4
0x065c9d…c394
2 touches
0 conflicts
0x3972b1f5…f153
0x065c9d…c394
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
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:
0x34b6552d…112a6f
1 conflict on slot
0x2395107727…b6539b
Audit this contract →
← previous block
·
next block →
recent activity