pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,218,519
← previous block
next block →
recent activity
Analyzing
Block #74,218,519
10 transactions · 7 stateful · 2026-05-13 01:11:33 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,218,519
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
exactInputSingle
#4
0xcf7468f4
#5
0x1094dc9f
#6
0x6a03d03d
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10f23c40…9a82
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
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:
0xd32edf66…9fff58
1 conflict on slot
0x10f23c4052…dd9a82
Audit this contract →
← previous block
·
next block →
recent activity