pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,640,880
← previous block
next block →
recent activity
Analyzing
Block #73,640,880
8 transactions · 7 stateful · 2026-05-10 08:49:46 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,640,880
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6a004722
#2
0x98717539
· blocks 3
#6
updateDataFeedsValuesPartial
#7
setData
#3
0x98717539
· blocks 2
#4
0x98717539
· blocks 1
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0x689cd5fd…5556
0x34b655…2a6f
6 touches
3 conflicts
0xa8bd52b5…862e
0x34b655…2a6f
6 touches
3 conflicts
0xfff38d9f…7063
0x8d66a4…3095
6 touches
3 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
5 touches
3 conflicts
0x8a35acfb…d19b
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
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
6 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity