pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,648,925
← previous block
next block →
recent activity
Analyzing
Block #73,648,925
15 transactions · 11 stateful · 2026-05-10 09:43:56 UTC
Parallelism
87
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,648,925
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#3
0x6a0053d4
#4
0x6a0053d4
#5
0xef555769
#6
0x05ee6a22
#7
0x05ee6a22
#8
updateDataFeedsValuesPartial
#9
updatePrices
#10
setData
#11
0x62be7533
#12
0x0c7abd22
#13
forward
#14
0x39435dac
#2
execute_route
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0005
0x5afd3e…7620
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:
0x3bd359c1…15433a
1 conflict on slot
0xd77e90ecbe…1e8c04
Audit this contract →
← previous block
·
next block →
recent activity