pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,951,326
← previous block
next block →
recent activity
Analyzing
Block #74,951,326
10 transactions · 8 stateful · 2026-05-16 10:42:19 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,951,326
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
updateDataFeedsValuesPartial
#3
0x39abec6b
#4
0xed82b078
· blocks 1
#6
release
#7
createGame
#8
setData
· blocks 1
#5
0xed82b078
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0230870e…327e
0x2ab50b…5c41
2 touches
0 conflicts
0x07d64d54…6bfc
0x2ab50b…5c41
2 touches
0 conflicts
0x0b2489bd…6d05
0x2ab50b…5c41
2 touches
0 conflicts
0x0ca4d360…a141
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
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