pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,041,889
← previous block
next block →
recent activity
Analyzing
Block #73,041,889
14 transactions · 10 stateful · 2026-05-07 14:23:18 UTC
Parallelism
86
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,889
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
0x98717539
· blocks 1
#9
0x0c7abd22
#10
updateDataFeedsValuesPartial
#11
0x69fca0ce
#12
0xeffdedb0
#13
setData
#3
updatePrices
#8
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a5
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x870d482a…3f9a
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
3 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
3 touches
1 conflict
0x313f2565…5b00
0x34b655…2a6f
2 touches
0 conflicts
0x32ee90db…decc
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:
0x8d66a43f…113095
1 conflict on slot
0x8a35acfbc1…6bd1a5
Audit this contract →
← previous block
·
next block →
recent activity