pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,981,575
← previous block
next block →
recent activity
Analyzing
Block #73,981,575
12 transactions · 10 stateful · 2026-05-11 22:53:20 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,981,575
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98c6107a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x98717539
· blocks 1
#8
0xed82b078
#9
0x6a025e57
#10
setData
#11
jMMeC
#2
0x98c6107a
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x1608635c…d25d
0x34b655…2a6f
4 touches
1 conflict
0x5d4efdae…7c73
0xa7283d…0ace
2 touches
0 conflicts
0x5d4efdae…7c74
0xa7283d…0ace
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity