pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,389,270
← previous block
next block →
recent activity
Analyzing
Block #74,389,270
12 transactions · 11 stateful · 2026-05-13 20:07:14 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,389,270
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
updateDataFeedsValuesPartial
#3
forward
#4
exactInputSingle
#5
0x5339c59f
#6
0x5339c59f
· blocks 1
#7
0xed82b078
#9
setData
#10
0x39435dac
#11
0x39435dac
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x195b037f…e0f6
0x34b655…2a6f
2 touches
0 conflicts
0x1c389468…6b0e
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity