pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,176,407
← previous block
next block →
recent activity
Analyzing
Block #73,176,407
8 transactions · 7 stateful · 2026-05-08 05:18:11 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,176,407
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x98717539
· blocks 1
#5
setData
#6
0x69fd728b
#7
0xeffdedb0
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x9d1bb389…c7d9
0x8d66a4…3095
4 touches
1 conflict
0xe72962f6…e169
0x8d66a4…3095
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x251861eb…78fd
0x34b655…2a6f
2 touches
0 conflicts
0x86c18027…d23d
0x34b655…2a6f
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
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity