pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,195,974
← previous block
next block →
recent activity
Analyzing
Block #75,195,974
8 transactions · 7 stateful · 2026-05-17 13:56:26 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
#75,195,974
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
transfer
#5
updateDataFeedsValuesPartial
#6
0x98717539
#7
setData
#2
swapWithBackendSignature
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
0xc8894e05…d43f
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04481809…1694
0x065c9d…c394
2 touches
0 conflicts
0x20795e18…fd14
0x065c9d…c394
2 touches
0 conflicts
0xafd5f258…5673
0x065c9d…c394
2 touches
0 conflicts
0xb48e72d7…3bc1
0x065c9d…c394
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
0xc8894e059a…95d43f
Audit this contract →
← previous block
·
next block →
recent activity