pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,960,662
← previous block
next block →
recent activity
Analyzing
Block #73,960,662
8 transactions · 8 stateful · 2026-05-11 20:33:22 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,960,662
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39ecce49
#2
forward
#3
0x6df9e92b
· blocks 2
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x6df9e92b
· blocks 1
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xed8924…7777
6 touches
3 conflicts
0x7b1b74a7…9206
0x3bd359…433a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x41be85…e2bd
6 touches
3 conflicts
0x00000000…0001
0x41be85…e2bd
6 touches
3 conflicts
0x072430d8…35ad
0xed8924…7777
6 touches
3 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
0xed892450…ab7777
3 conflicts on slot
0x44ad89ba62…49cf83
Audit this contract →
← previous block
·
next block →
recent activity