pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,766,574
← previous block
next block →
recent activity
Analyzing
Block #74,766,574
17 transactions · 12 stateful · 2026-05-15 14:09:06 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,766,574
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
updatePrices
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x1a945f9c
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
withdraw
#9
0x6df9e92b
#10
forward
#11
0xed82b078
· blocks 1
#13
0x6a072979
#14
setData
#15
0x39435dac
#16
0x39435dac
#12
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x4060605b…75a3
0x3bd359…433a
2 touches
0 conflicts
0x57a37dda…8712
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0002
0x91b81b…6d56
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity