pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,951,356
← previous block
next block →
recent activity
Analyzing
Block #74,951,356
10 transactions · 6 stateful · 2026-05-16 10:42:31 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,951,356
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a084a8f
#2
updateDataFeedsValuesPartial
#3
0x0c7abd22
· blocks 1
#4
0xc5a04723
#6
setData
#7
0xdc0566…4f06
#8
0x4ee299…7468
#9
0x137af4…4d64
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x79d67338…ed27
0x065c9d…c394
2 touches
0 conflicts
0x92c2a472…d53f
0x065c9d…c394
2 touches
0 conflicts
0xa66dda53…38f9
0x065c9d…c394
2 touches
0 conflicts
0xaae952ce…798c
0x065c9d…c394
2 touches
0 conflicts
0xc3b5c80f…b7ab
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity