pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,404,705
← previous block
next block →
recent activity
Analyzing
Block #74,404,705
11 transactions · 10 stateful · 2026-05-13 21:50:01 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,404,705
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a04f280
#2
exactOutputSingle
#3
execute
#4
0xed82b078
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
0x6a04f280
#9
setData
#10
0x39435dac
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x345667db…c4b7
0x065c9d…c394
4 touches
1 conflict
0xf6d7f7d1…37a1
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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
0x345667db6e…7fc4b7
Audit this contract →
← previous block
·
next block →
recent activity