pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,473,868
← previous block
next block →
recent activity
Analyzing
Block #73,473,868
11 transactions · 10 stateful · 2026-05-09 14:17:28 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,473,868
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5de3085d
· blocks 3
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#10
_callMultipleTargets
#2
0x5de3085d
· blocks 2
#3
0x5de3085d
· blocks 1
#4
0x5de3085d
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
0x8fa7a69c…8fd7
0xc2a771…7777
8 touches
6 conflicts
0x536e2740…61ac
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0002
0xa7283d…0ace
8 touches
6 conflicts
0x5a852fa4…442c
0xa7283d…0ace
8 touches
6 conflicts
0x5a852fa4…442d
0xa7283d…0ace
8 touches
6 conflicts
0x5a852fa4…442e
0xa7283d…0ace
8 touches
6 conflicts
0x5a852fa4…442f
0xa7283d…0ace
8 touches
6 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:
0xc2a7715d…3d7777
6 conflicts on slot
0x8fa7a69c55…388fd7
Audit this contract →
← previous block
·
next block →
recent activity