pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,969,753
← previous block
next block →
recent activity
Analyzing
Block #74,969,753
15 transactions · 13 stateful · 2026-05-16 12:46:22 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,969,753
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x575c0012
#2
0x6a086796
#3
execute
#4
exactOutputSingle
#5
exactOutputSingle
#6
execute
#7
0xed82b078
· blocks 1
#9
0xe7be4706
#10
0x98717539
#11
updateDataFeedsValuesPartial
#12
setData
#13
0x39435dac
#14
0x39435dac
#8
0x1ffa3c9b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x0e0186da…44cb
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
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity