pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,924,972
← previous block
next block →
recent activity
Analyzing
Block #75,924,972
7 transactions · 6 stateful · 2026-05-20 23:10:18 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,924,972
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4ec9f7a2
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateTemporalNumericValuesV1
#5
setData
#6
0x39435dac
#2
0xed82b078
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
0xe5903d01…c345
0x065c9d…c394
4 touches
1 conflict
0x7c5e1bc7…0399
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x47a5b3ac…e4e4
0x065c9d…c394
2 touches
0 conflicts
0xaf807bd0…4482
0x065c9d…c394
2 touches
0 conflicts
0x09d2858d…dcea
0x2a68ba…90c5
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x7301f2af…c48e
0x2a68ba…90c5
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
0xe5903d018b…dcc345
Audit this contract →
← previous block
·
next block →
recent activity